I have devoloped a DB in access 2000. I have used developer to create a package that will deploy with the Access 2000 runtime. The problem that I encounter is that most of the users that will be installing this DB are running Office 97. When the Access 2K runtime installs on the system it does not damage the 97 install, it just reassociates all mdb files with the new runtime version.
I need to know how to customize the runtime installer so that it does not replace file associations and does not overwrite the 97 installs. If I should use VB to create the installer using a dependancy lists then I will go that route, but I need to find a good resource for information on creating access runtimes based on dependancies. It would be better if I could just restrict file associations though.
Thanks,
yeatmanj
I need to know how to customize the runtime installer so that it does not replace file associations and does not overwrite the 97 installs. If I should use VB to create the installer using a dependancy lists then I will go that route, but I need to find a good resource for information on creating access runtimes based on dependancies. It would be better if I could just restrict file associations though.
Thanks,
yeatmanj