Running Classic Forms in Sage ERP Accpac 6
One of the main features of Sage ERP Accpac 6.0A is a fancy new Web based desktop/portal to act as a new home page for Accpac users. This new desktop/portal includes new dashboards (https://smist08.wordpress.com/2009/12/) and reporting capabilities (https://smist08.wordpress.com/2009/12/11/sage-erp-accpac-6-0-adhoc-query/). This is the first step in a transition for Accpac from a traditional Windows desktop application to a true Web based application. For this first release the only accounting screen that have been “webified” are the various quote and order related screens that are run inside SageCRM (https://smist08.wordpress.com/2009/12/17/sage-erp-accpac-6-0-quote-to-orders/). In the meantime we still want the new desktop/portal to be used by all users, so we have provided the ability to run the classic VB forms from the new desktop/portal.
The Tasks and Reports menu give you access to all the screens that are available in Accpac today.
Then when you click on “Order Entry”, the regular screen runs:
You can add any of these screens to the shortcuts bar for easy access:
When running these classic screens, they aren’t using the older Accpac Web Deployed mode, they are using Workstation Setup. This means the screens will run exactly the same as they run from the classic Accpac Desktop. The setup and configuration requirements for these screens are exactly the same as for the classic Desktop.
The classic Desktop is still included with the product and you can still use this, if you wish. Even once we have Web versions of our screens, we will still provide the classic VB screens as an option. This way you can move to the web at your own pace. You can move your customizations at your own pace and you can learn the new screens and transition over at your own pace. The new web based Accpac is still Accpac. All the business logic is exactly the same. The screens will still provide the same functionality as the classic product, but with usability improvements for learn-ability and productivity.
Of course, normally, a web page cannot run a VB ActiveX object. We also don’t want to work like the current Web Desktop where each VB screen is embedded in a web page and downloaded separately taking time and throwing up all sorts of security messages. So what we do is embed one small ActiveX control in our main web page whose responsibility is to run any of the Accpac OCX screens when requested. This way you only need to download and install one ActiveX control from IE. If you want to use this functionality you must use IE as your browser (it will simply be ignored in other browsers like Firefox). But hopefully this provides a simpler less painful mechanism to run our VB forms from IE than the current Web desktop.
Any third party ISV product written in the SDK and using VB based classic screens can provide XML configuration files, so they can run from the new desktop/portal as well. However we will only be running classic VB screens, we will not be running older CA-Realizer based screens nor general EXE programs. For these you will need to use the classic Desktop or run them directly from the Windows Start Menu. Since we are running these programs from an ActiveX control, we simply can’t open it up to run everything since this would be a huge security hole. We certainly can’t run arbitrary EXEs as this would be very exploitable by hackers.
This mechanism should provide an easy way for customers to transition from the VB world of Windows desktop applications to the newer more popular Web Based approach. Again, customers can move at their own pace. They can freely use both the new screens and old screens at once. They can keep using the VB screens and their current customizations for a long time (probably as long as Microsoft supports running them on Windows). And if some users prefer the Web screens and some prefer the VB screens, they can both happily co-exist.