VB5 VB6 DLL/OCX Version

[bwood]

We have just installed Visual Studio 6 Enterprise but still have many offsite users running apps developed with VB5. These users still have the DLL/OCX files from VB5. Now that I have VB6 installed, when I compile one of the user apps on my machine using the new DLL/OCX files and send the .EXE file to the users, they get the generic "unexpected error" message. I figured out that the problem was with the TABCTL32.OCX and got this problem fixed for now. I'd appreciate some words of wisdom on a stradegy to handle keeping DLL/OCX files in sync when upgrading development machines but not the user machines. Thanks for all suggestions.....

[bwood]

Any suggestions would be appreciated.........

[Lothar Haensler]

IMHO you should always create a Setup program for your app or an update of your app using PDWizard or the new Visual Studio Installer.
That way the relevant versions of DLLs and OCXs from your development machine will be incorporated into the setup for your program.