Doug Murphy
doug at murphyscreativity.com
Tue Nov 18 11:33:14 CST 2003
The way that Sagekey gets around the problem of Access trying to open a database in the last version of Access used when you have when you have several versions of Access on the same computer is to open the application through a small executable called runaccess.exe. This should be what your desktop shotcut calls, not Access.exe. If the runtime is opened through this method the registry setting that indicates what version of Access was used last is not supposed to be reset to your runtime version. If the shortcut goes directly to Access.exe then that is the problem. I'd contact tech support at Sagekey and have them work with you to resolve the problem. I have found them to be very helpfull. Doug Douglas Murphy Murphy's Creativity (619) 334-5121 doug at murphyscreativity.com www.murphyscreativity.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of rfv at entelix.com Sent: Tuesday, November 18, 2003 8:43 AM To: AccessD at databaseadvisors.com Subject: [AccessD] Sage RT script Hi, I hope somebody can help me. I purchased the Sage MS Access XP RT script. Now my cliente has Windows 2000 Pro and MS Access 2000 installed. When he clicks on the shortcut of my app, a error message appears stating that this application is not soported, wanting to open my app with Access 2000. So we have to go to the runtime folder, click MS Access XP .exe., but the problem is that he can not open his other Access 2000 db´s. Is the Sage script not supposed tu avoid all this? I hope somebody has the answer. Rudolf F. Vanek _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com