John Bartow
john at winhaven.net
Wed May 11 10:17:34 CDT 2011
Problems. Little if any support for 3rd party add-ins, Active X controls, etc. I installed it once (MSDN) and it made no difference in performance so I canned it. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach Sent: Wednesday, May 11, 2011 9:52 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 32 vs 64-bit John, >> Microsoft does everything they can to encourage people not to use it. >> << Fascinating. Why is that? Steve Erbach Neenah, WI On Wed, May 11, 2011 at 9:35 AM, John Bartow <john at winhaven.net> wrote: > Hi Darrell, > I'd be interested in the reason they use 64 bit Office. Microsoft does > everything they can to encourage people not to use it. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darrell > Burns > Sent: Wednesday, May 11, 2011 8: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? -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com