Darrell Burns
dhb at flsi.com
Wed May 11 11:44:17 CDT 2011
".do you provide a short cut that runs the Access file under your runtime install?" Hey Doug. I didn't explicitly create a shortcut but why would that matter? --DB -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Wednesday, May 11, 2011 9:17 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access 32 vs 64-bit Darrell, If your providing a runtime why is the app. trying to run from Access 64? Your runtime should run independently of the installed version. When you install the runtime do you provide a short cut that runs the Access file under your runtime install? Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darrell Burns Sent: Wednesday, May 11, 2011 6:03 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access 32 vs 64-bit Hello. I developed a 32-bit Access 2007 app with VBA code that uses DAO exclusively for data access and has no add-ins. My client has Windows 7 64-bit PCs running Office 2010 64-bit. I delivered the app as a 2007 runtime package and it didn't work at their place. The app runs fine on my WinServer2008 machine with Office 2010 32-bit, but I haven't tested it under Office 2010 64-bit. Since my other clients are still operating in the 32-bit world, I can't abandon the 32-bit version. Is there a way to satisfy both worlds with just one version? Thanx, DB -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com