Mainly the Sage 300 customization are done using OCX, VBA Macros and the executable. In this blog we are going to discuss what the differences in these two approaches are.
New Stuff: IC Reorder Quantity in Sage 300
Below listed are the differences between customization approaches using OEX and MACROS:
1. As the customization using OCX is basically a source code modification rather macro is enhancement to the original functionality without changing its basic source code.
2. Macros cannot able to alter the Sage 300 core business logic as well database structure.
3. The macros are also called as “upgrade safe” as it does not deal with database specification changes where in case of OCX it may require the long process including installations etc. So the Sage 300 version upgrades or product updates rarely need changes in the macros where as OCX need to be rebuild in that particular version.
4. Macro generally minimizes the development time rather than to use the traditional approaches for the customization of source code as the macro can access the Sage 300 session and error handling etc. This helps in minimizing time efforts for the changes.
5. Macros can be easily added to the Sage 300 desktop without any changes to roto.dat and grp.dat files where as in case of the customization using OCX requires modification to “roto.dat” and “grp.dat” file.
1. Though it takes less efforts and time using macro for the source code customization still it depends on the technical efficiency and the complexity of the functionality.
2. However, OCX provides more flexibility in using Sage 300 controls such as accpacgrid etc. i.e. macros facilitates limited control on the Sage 300 objects.