Doug Murphy
dw-murphy at cox.net
Tue Feb 13 11:43:15 CST 2007
This is a reason to use the Sagekey scripts to build runtime installations. The script addresses this issue by opening the runtime database through an intermediary program "runaccess.exe" that takes care of the associated registry settings with the appropriate time delays so they stay set. You could do the same thing, but would probably have to experiment with which settings to work with and when to set them in relation to programs start. There may be more info on the Sagekey site. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Skolits Sent: Tuesday, February 13, 2007 6:03 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access file association switching between Runtime andFull Access When I open a Runtime version of access, the file association changes so the next time someone runs any MDB file, it tries to run 'Runtime', even though they also have a full version on their PC. I've found two registry settings that I could possibly modify every time I close my Runtime version. Anyone run into this before? Is this the best way to go? Registry entries: HKEY_CLASSES_ROOT\Access.Application.10\shell\Open\command Data: "C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" /NOSTARTUP "%1" ----- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Access.Application.10\shell\Open\command Data: "C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" /NOSTARTUP "%1" Thanks, John -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com