Microsoft Access 2003 developer extensions Package Wizard Problem
Posted on 2009-04-27
I have a client who wanted a database application but did not want to purchase copies of access for each computer running the application.
So, using the developer extension package wizard I created a nice installable package which includes the runtime modules for access. All installed and worked great and the client was very satisfied. It is time to update the application and a very frustrating problem arises. I am able to create a new package and CD with no problem. When the application is installed on the computer, it says the old one must be uninstalled, so I get the original CD and uninstall the application, no problem.
I now install the updated version of the application, the installation goes fine, and all seems well. The new updated application is open and it looks just like the old application. I uninstall and reinstall several times with the same results. Thinking for some reason the old application is still located on the hard drive somewhere; I find and delete any reference to the old application. I even create a new title, name, and new installation directory and repackage the application, just to install and get the same result. I am assuming this has to do with the registry but I do not really know. So, I need to know why the old application is still being open when no copy of the old application exists on the hard drive anywhere. The application is written and packaged in MS Access 2003 and Windows XP home. The application is being installed on a Windows Vista Home Premium machine. Anyone with knowledge and experience using the developer extensions package wizard would be appreciated.