Compatibility of A2007 running on XP x86 and XP x64 systems

[mdlueck]

I discovered that some workstations are loaded with Windows XP x64 edition, and still running Office 2007 which is x86 only.

In my Access application I make extensive use of:

• ADO/ADOX objects

References include:

• Visual Basic for Applications
• Microsoft Office 12.0 Object Library
• OLE Automation
• Microsoft Office 12.0 Access database engine Object Library
• Microsoft ActiveX Data Objects 2.8 Library
• Microsoft ADO Ext. 2.8 for DDL and Security
• Microsoft Office 12.0 Object Library

• DAO.QueryDef objects in Pass-Through mode

• A handful of calls to DLL API's:

http://support.microsoft.com/kb/186063
http://www.programmersheaven.com/mb/vba/371593/371593/change-registry-settings-in-vba/
are the ones I can spot I have used right off.

I distribute the application in its .accdb form.

What should I anticipate from running the application on the XP x64 OS platform?

 

[thechazm]

Your problably not going to run into complications with just that due to most of those references are internal to the office product will be X86 but if you work with any outside connections trying to connect to a SQL server or Oracle your in for a little bit of a headache due to the differences between the operating systems.

This is just my 2 cents.

 

[mdlueck]

but if you work with any outside connections trying to connect to a SQL server ...

Oops, forgot to mention... I make use of a DSN'less connection to a SQL Server 2008 R2 BE DB.

So, is 32-bit Access 2007 not going to want to play nice with the 64-bit SQL Server ODBC driver or something?

 

[thechazm]

Thats correct because the ODBC drivers require different parameters and setup's to make them work. Plus they removed a ton of ODBC drivers from the 64 bit version and mostly focused on letting Jet do the job.

It is a royal pain but it can be done.

 

[mdlueck]

and mostly focused on letting Jet do the job.

But Jet is DAO, so where does that leave ADO code? I make extensive use of ADO.Command / ADO.Parameters / ADO.Recordset objects. And ADOX as well.

 

[thechazm]

There for a while when it initially released it was almost impossible to get it to work so mostly everyone tried using the 32 bit development and code to keep it working under a 64bit OS. Even then there were conversion problems and hangups with the 32bit version due to the way it deals with connections.

Supposivlely (sorry no time for spell check) with the office 2010 64bit edition it's supposed to contain a 64bit version of ADOX. I cannot confirm this as I do not have that version but that's what was on the streets.

With Windows XP you might be able to get away with just developing in a 32 bit environment and the 64bit ones will only run it in 32 bit mode but you are expecting on the OS to focus all your connections in 32bit.

Here is a website that talks about the woes a little bit but honestly your not going to know until you do a test. I wish you the best of luck though.

http://stackoverflow.com/questions/3053136/access-ado-64-bit

 

[thechazm]

Forgot to mention the purpose of the 64bit changes in the connections was to make people focus on using the ACE connection objects but not everyone wants that.

Another little 2 cents.