My company has been successfully selling and deploying an Access 2000 runtime application over the past 9 years. We use a Wise InstallBuilder 8.14 to package and deploy the front-end, back-end, and associated runtime files. We plan to move to Access 2007 or Access 2010 as soon as we can, but in the mean time, we have orders to fill using the old Ac2000.
Recently a customer of ours purchased a new laptop with Vista Home Premium 64-bit, to replace his old WinXP laptop which had been running our app for about two years. We did a remote session and ran our installer and it loaded without any problems. However, when we started our app via its desktop icon, we got the following Microsoft Office error message: "This application must be installed to run. Please run Setup from the location where you originally installed the application."
Our application has installed flawlessly in Win98, Win2000, WinXP, and Vista (32 bit) operating systems. I don't recall if the customer's laptop may have already had a trial version of the Office 12 suite installed or not.
Here is the icon's target path: "C:\Program Files (x86)\Microsoft Office\ART\Office\MSACCESS.EXE" /excl /runtime /wrkgrp "C:\Harvest Biomed\system.mdw" "C:\Harvest Biomed\HarvestCEMS.mde" The runtime files did in fact install in C:\Program Files (x86)\Microsoft Office\ART\Office
I may be wrong, but I suspect that the problem is with the Vista 64 registry settings. Using Regedit to open the Vista 64 Registry, I noticed that the company and product keys were missing under the HKEY_LOCAL-MACHINE / SOFTWARE section. I suspect that there should also be registry entries under the HKEY_LOCAL-MACHINE / SOFTWARE / Classes section and the HKEY_LOCAL-MACHINE / SOFTWARE / Classes / Installer / Products section, but I don't know what the differences are between a 32 bit and 64 bit registry.
This is the first time that we have tried to install our app on Vista 64 bit. Not only do we need to get our customer's application installed and running on his new laptop, but we also need to know what changes that need to be made in our installer scripts to handle future Vista 64 bit installs. Thanks
Recently a customer of ours purchased a new laptop with Vista Home Premium 64-bit, to replace his old WinXP laptop which had been running our app for about two years. We did a remote session and ran our installer and it loaded without any problems. However, when we started our app via its desktop icon, we got the following Microsoft Office error message: "This application must be installed to run. Please run Setup from the location where you originally installed the application."
Our application has installed flawlessly in Win98, Win2000, WinXP, and Vista (32 bit) operating systems. I don't recall if the customer's laptop may have already had a trial version of the Office 12 suite installed or not.
Here is the icon's target path: "C:\Program Files (x86)\Microsoft Office\ART\Office\MSACCESS.EXE" /excl /runtime /wrkgrp "C:\Harvest Biomed\system.mdw" "C:\Harvest Biomed\HarvestCEMS.mde" The runtime files did in fact install in C:\Program Files (x86)\Microsoft Office\ART\Office
I may be wrong, but I suspect that the problem is with the Vista 64 registry settings. Using Regedit to open the Vista 64 Registry, I noticed that the company and product keys were missing under the HKEY_LOCAL-MACHINE / SOFTWARE section. I suspect that there should also be registry entries under the HKEY_LOCAL-MACHINE / SOFTWARE / Classes section and the HKEY_LOCAL-MACHINE / SOFTWARE / Classes / Installer / Products section, but I don't know what the differences are between a 32 bit and 64 bit registry.
This is the first time that we have tried to install our app on Vista 64 bit. Not only do we need to get our customer's application installed and running on his new laptop, but we also need to know what changes that need to be made in our installer scripts to handle future Vista 64 bit installs. Thanks