I wonder if anyone out there has deployed a solution successfully like mine?
I have created a vb.net 2005 winform solution that can be installed on a desktop.
It uses an access 2003 database to hold data. The setup.msi was created using the vs.net
deployment menus. The solution uses access reports to show lots of different reports, basically because the reporting package in VB.net, in my opinion, isnt anywhere near as good as reports in access. Access 2003 runtime is used and installed if the client PC hasnt got Access 2003. It isnt installed if the client has Access 2003.
Everything deploys OK as long as the client pc hasnt got any other version of access.
If the client has Access 2000 however, although the connections work allowing data to be viewed, added, updated and deleted, the reports wont work giving error 429, cannot create Activex object. I presume the deployed solution is getting confused about which MSACCESS.exe to use as there is more than 1 present. Invariably its going for the wrong version!
Has anyone figured out a way of testing to see if there are more than 1 msaccess.exe present and if so to select the correct one to use? Any advice would be great as I am a bit stuck currently.