In Sage 300 ERP, user might come across some complicated error messages while opening screens (UI). In this blog we will discuss about one of the common errors while opening the customized screen or a third-party module screen. Many times, when standard Sage 300 screen is customized by the third party by adding some additional… Read More: Possible cause for issue: “Error code -2147221164 class not registered” »
Sage 300 provides a functionality to customize sage 300 standard screen or to create a custom module as per the business requirement. Whenever an additional functionality is required in standard Sage 300 the custom module is created with a customized OCX screen. With this custom module creation and customized screens, we have to maintain its… Read More: Possible cause of “object is not defined in roto event… »
In this blog, we will discuss about the solution for the warning message while loading the customized screen (OCX) I.e. ”AccpacOE1000.ocx could not be loaded”. Sage 300 provides an SDK (Software Development Kit) using, which a developer can customize, existing OCX screens, which has different OCX, name than that of standard name. Sometimes when any… Read More: OCX could not be loaded »
Sage 300 provides an SDK using which a developer can customize an existing OCX screen. This customized screen needs to be upgraded with a higher version of sage 300 when you upgrade your Sage 300 to higher version. While upgrading this customized source code with a higher version and making the OCX, sometimes we can… Read More: Error: Permission Denied while making OCX »
We are familiar that Sage 300 ERP allows customizing the standard screens, which has different OCX name than that of standard name. Whenever we perform some type of customization in sage 300, which has new screen files and other dependent files, user needs to register the same in windows. Sometimes when we change only few… Read More: Error while registering an OCX in Sage 300 »
Sage 300 provides an SDK using which a developer can customize an existing OCX screen. This customize screen needs to be upgraded with a higher version of sage 300 when you upgrade your Sage 300 to higher version. While upgrading this customized source code with a higher version and making the OCX, sometimes we face… Read More: Unable to set the version compatible component »
Sage 300 provides us the feature to disable the maximize box on the top right corner which is present in between the close and minimize option. There are situations or requirements when we need that user should not have the power to use the maximize feature of the screen i.e. user should not be able… Read More: Disable Maximize Box in OCX »
Sage 300 provides an SDK using which a developer can customize an existing OCX screen. This feature is most important as most of the user needs some kind of changes in the screen to automate the process and increase the productivity by reducing the user intervention wherever unnecessary. So, customizing an OCX screen also requires… Read More: Localized resources aren’t available »
Here we are going to discuss about the issue that causes the Sage 300 customized screen to display unnecessary “UAC popup” prompt when the sage 300 is logged in by non-administrative window user. We have come across this issue mostly in Windows 10 and later versions environment due to advanced security measures that has been… Read More: Possible Cause and Resolution for UAC popup while opening Sage… »
Sage 300 classic desktop provides various user interfaces i.e. screens which are basically OCX files i.e. “ActiveX Control Objects”. The entry screens generally has windows maximize and minimize buttons but for Report user interfaces or those user interfaces on which no tabular data or grid present the maximize button might been disabled. While customizing these… Read More: Sage 300 -Allowing Only Minimize Box on Customized OCX »
