Access Developer Deployment Problem

[Timbo99]

I have been using the deployment wizard( developer XP), seems to work great..
I do have one problem though.. it seems if the access runtime program is installed on a computer with an earlier version of access, the user will be forced to use the viewer for his own personal access databases.. What happened to the previous version of access?.. is there a way to have the viewer only active for the program I made in access 2002, and not disrupt their own files in access 97?

It wants to convert there files to 2002... hummm

Thanks

 

[Sorrells]

Timbo99,

This is a known problem with the MS Developer product. (Pat, hit me if I am wrong! There is always the possibility of conflict if a Runtime Access version is placed on a PC that has a native Access of a different version. I believe the story is that the last instance of an Access version that ran will be invoked against any database on the PC. Thus if you ran Runtime A2K then decided to open a A97 dB, A2K would attempt to open it and want to convert it.

These problems have led to advice for another 3-party product. Most in demand are Sagekey, Wise and then InstallShield.

I'd recommend that you perform searches on all of these in this forum and you should gain some insightful information.