I am still running BV 2004. When it was transferred to a new server the code had issues that I haven't been able to figure out. With that said, the discount and sales choices under "catalog" is not working. Which is a huge issue.


When I try to "add a new discount' it just comes up with "error while trying to add new discount", yet when I try to edit an existing discount this comes up:



Can anyone help???? I realize we will have to look at upgrading to a newer BV but for now we need some help.




<H1>
</H1>
<H2>[color=#ffffcc>

[tr ][td ]<CODE>
Line 1: &lt;%@ Control Language="vb" AutoEventWireup="false" Codebehind="CategoryPicker.ascx.vb" Inherits="CategoryPicker" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %&gt;
[/color]Line 2: &lt;P&gt;
Line 3: &lt;asp:DataGrid id="dgCategories" runat="server" AutoGenerateColumns="False"&gt;</PRE>[/code][/td][/tr]</TABLE>
Version Information: Microsoft .NET Framework Version:1.1.4322.2443; ASP.NET Version:1.1.4322.2470 </FONT>&lt;!--
[HttpException]: Could not load type 'CategoryPicker'.
at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase)
at System.Web.UI.TemplateParser.ProcessMainDirective(IDictionary mainDirective)
at System.Web.UI.TemplateControlParser.ProcessMainDirective(IDictionary mainDirective)
at System.Web.UI.TemplateParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.TemplateParser.ParseStringInternal(String text)
at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir)
[HttpParseException]: Parser Error: Could not load type 'CategoryPicker'.
at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir)
at System.Web.UI.TemplateParser.ParseFile(String filename, String virtualPath)
at System.Web.UI.TemplateParser.Parse()
at System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation()
at System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound)
at System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath()
at System.Web.UI.TemplateControlParser.GetReferencedType(TemplateControlParser parser, String virtualPath)
at System.Web.UI.TemplateControlParser.GetUserControlType(String virtualPath)
at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.TemplateParser.ParseStringInternal(String text)
at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir)
[HttpException]: Parser Error: Parser Error: Could not load type 'CategoryPicker'.
at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir)
at System.Web.UI.TemplateParser.ParseFile(String filename, String virtualPath)
at System.Web.UI.TemplateParser.Parse()
at System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation()
at System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound)
at System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath()
at System.Web.UI.TemplateParser.GetParserCacheItem()
at System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageParser.GetCompiledPageInstanceInternal(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String path)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, String path, String pathTranslated, Boolean useAppConfig)
at System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
--&gt;&lt;!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using &lt;customErrors mode="Off"/&gt;. Consider using &lt;customErrors mode="On"/&gt; or &lt;customErrors mode="RemoteOnly"/&gt; in production environments.--&gt;