Going round in circles.
Have packaged my first Access 2010 runtime applcation no problem at all.
It's a very simple one file Front End.

I have now updated, and built a new installation pack, but when I try ti install it, the PC telss me that Another version is already installed, and that I need to go to the control panle (XP by te way) and unsintall from there.
Trouble is that the app doesn't appear in the list. - Access 2010 runtime did, and that uninstalled just fine.

But it still thinks that 'something is installed and I can't find it!.

I ahve rather cleverly (?????) overwritten the original instal pack with my new one.

If I right click on the MSI I get three options:
Install: Can't do this because another version is already installed
Repair: Can't do this because the action is only valid for products that are currently installed
Uninstall: Can't do this because anothe version is installed and must be remoived via the add/install on the control panel.

So an ideas how to remove the old one so I can put the new one in.

And for future updates is there any reason why I shouldn't simply replace the accdr with the latest accdb and tweak the shrotcut?


Many thnaks for any pointers.

I found an answer to the uninstall problem.

A search through the registry looking for the string of the app name, which was fortunately all consonants, and double checking the Product coded allocated by the wizard, allowed me to delete all the keys in question. -- But I can't help but think that the packager should have left the app in a state where it could be uninstalled without having to delve through the registry.

Of course this just leads to more questions: There is an apparently useful hyperlink in the wizard "Learn about when to change the Product Code or Upgrade Code" , which pops up an Access helps screen whihc offers no help on the subject at all.

Is the fact that the app doesn't appear in the list of program that are installed, deliberate or a bug I wonder?

As far as I can now tell, all I actually need to do is to install the runtime on machines without Access, and copy the accdb to the client machine, for a fairly reliable and painless support process. - This doesn't give all the fancy screens, but it does at least seems to work reliably.

I agree with your. The Access Package and deployment wizard really is not good for updating your database.


You use the Access P&D wizard to create the initial installer package. I would use an auto updater to install the updated. I place the updated front end in a to a location on the server. I use a folder in the same location as the back end.