Upgrading Custom Programs in Microsoft Dynamics SL

One concern when upgrading to a new Microsoft Dynamics SL version is any custom programs. Custom programs will need to be upgraded to the new version as well. Depending on which SL version is the source and which is the destination, this process can either be easy or involved. It has become more complicated in the newer versions than it used to be.

Solomon 4.0 → Dynamics SL 6.5

Between Solomon version 4.0 and Dynamics SL 6.5, custom programs were written in VB6 and upgrading them is a simple process. First, replace the DH files containing the table buffer definitions; technically, that only needs to be done if the table definition changed, but making that change universal is faster and easier. Then, do the same thing with the applic.dh and swimapi.bas files, recompile, and the upgraded program is ready for use. It is possible that some other changes might be needed. For example, if a field was lengthened, the screen may require adjustments, and new fields may need to be added, but these are unusual circumstances.

Dynamics SL 6.5 → Dynamics SL 7.0

Changing from SL version 6.5 to 7.0 was MUCH more involved. That upgrade involved changing from VB6 code to VB.Net. Fortunately, Dynamics provided a utility that would manage much of the process. Running SolomonSDKConversionUI.exe for each project to be converted started the process.