Here's a question for the Accpac vb6 programmers.
The programs my company creates has various code segments to determine whether specific code is required for a specific versions of Accpac. For example, our finders have code to determine if we need to reference views from 5.4 or 6.0 (which can affect certain column names or view compositions depending on the Accpac version). Doing it this way allows us to maintain only a single copy of the program.
A former long time employee for the company indicated that each version of accpac has its own 'entry points'. Therefore, what we've been doing for years is that we have one program which we import into separate development environments (eg. a development environment running Accpac 5.4, a development environment running Accpac 5.5, a development environment running Accpac 5.6, etc.). Once we make a change, the program is run from the development environment to test the change. If all is successful, then the program is compiled into an exe and we use another program to create a setup file for each associated accpac environment (A setup file for users of Accpac 5.4, a setup file for users of Accpac 5.5, etc). This has been working fine but it is very tiresome moving files back and forth each time we make a new build of the program.
Here's my question, if the change is minor and doesn't affect a certain version of accpac (say for simplicity sake, we add a section to test for a null string reference), and the change was originally made in the development environment for Accpac 5.4, do we really need to import the vb6 program into each of the v5.5, v5.6 and v6.0 environments to recompile the program in the version specific environments?
Thanks.
If at first you don't succeed, then sky diving wasn't meant for you!
The programs my company creates has various code segments to determine whether specific code is required for a specific versions of Accpac. For example, our finders have code to determine if we need to reference views from 5.4 or 6.0 (which can affect certain column names or view compositions depending on the Accpac version). Doing it this way allows us to maintain only a single copy of the program.
A former long time employee for the company indicated that each version of accpac has its own 'entry points'. Therefore, what we've been doing for years is that we have one program which we import into separate development environments (eg. a development environment running Accpac 5.4, a development environment running Accpac 5.5, a development environment running Accpac 5.6, etc.). Once we make a change, the program is run from the development environment to test the change. If all is successful, then the program is compiled into an exe and we use another program to create a setup file for each associated accpac environment (A setup file for users of Accpac 5.4, a setup file for users of Accpac 5.5, etc). This has been working fine but it is very tiresome moving files back and forth each time we make a new build of the program.
Here's my question, if the change is minor and doesn't affect a certain version of accpac (say for simplicity sake, we add a section to test for a null string reference), and the change was originally made in the development environment for Accpac 5.4, do we really need to import the vb6 program into each of the v5.5, v5.6 and v6.0 environments to recompile the program in the version specific environments?
Thanks.
If at first you don't succeed, then sky diving wasn't meant for you!