Sounds like it's the merge modules not being deployed properly. I would go back and check the setup.exe program to see how its built.

There is also a chance it could be a versioning problem. I don't know how often you 'tweak' your box and install updates, but if you feel confident that your setup.exe is built correctly, then I would go to the BOBJ support site and download the latest service pack and merge modules. Install both on your machine and test and rebuild the setup. This would ensure that the versioning is clean.


Edited by BrianBischof - 03 Aug 2007 at 9:39am

If you're brand new to CR.NET 2003, you should pick up a copy of my book. I explain all this and give you lots of tips and tricks to save you headaches.

Anyway, the reason that it works on your computer on not the destination computer is that since you built the application on your computer, you have all the necessary libraries installed. What you are missing is these same libraries in the Setup.exe program. The Merge Modules are separate from what you have on your computer. They are complete files with every DLL needed to run CR.

What I would do is install the latest CR SP as well as get the matching merge modules on your computer. Then rebuild the app and create a Setup app using the new merge modules.