Question Access 2010 Runtime x64 vs Access 2000 x32 Problem

[Lee D]

Hi All,

You will need to excuse my lack of techno jargon, as I am a relative noob when it comes to Access.

At my work pretty much all of our machines are running either Office 2007 or 2010 without MS Access (or trial version only installed). To overcome this I have disributed MS Access Runtime relevant to the version of MS office and the type of machine the user has eg Office 2010 on a x32 machine has AccessRuntime.exe and on x64 machines with Office 2010 they have AccessRuntime_X64.exe loaded from the MS download centre.

We have recently purchased a database for the business which was developed in MS Access 2000 32-bit version.

I have configued ODBCAD32 to allow us access to the SQL server where all the data is currently held, on all machines - this being the SQL connection to the offsite server.

It works without any issues on the x32 machines however on x64 I keep getting the message:

"The database was created with the 32-bit version of Microsoft Access. Please open with the 32-bit version of Microsoft Access."

I cannot run the 32-bit version of Office 2010 runtime on the 64-bit machines.

Is there a work around for this?

 

[Pat Hartman]

Access 2010 32-bit and 64-bit are not compatable. Stick with an all 32-bit environment for now. There is no benefit to using the 64-bit version of Office unless you need humongous Excel spreadsheets but the cons are plenty starting with losing most if not all of your addins and having to change any code that calls the Windows API.

There is no problem runnin the 32-bit version of Office on 64-bit machines. You must run a 64-bit operating system (Windows) but other software can be 32-bit.

 

[Lee D]

Access 2010 32-bit and 64-bit are not compatable. Stick with an all 32-bit environment for now. There is no benefit to using the 64-bit version of Office unless you need humongous Excel spreadsheets but the cons are plenty starting with losing most if not all of your addins and having to change any code that calls the Windows API.

There is no problem runnin the 32-bit version of Office on 64-bit machines. You must run a 64-bit operating system (Windows) but other software can be 32-bit.

So does this mean I should uninstall Office 2010 x64 from the 64-bit machine and re-install as 32-bit?

I did come up with one solution, it wasn't the best but it worked (ish) I installed MS Access 2007 runtime and pointed the MS access 2000 database to use this as the default program.

The only issue I had was the internally developed MS Access 2007 database which will be run in tandem with the externally purchased MS access 2000 database now use runtime 2010 and runtime 2007 respectfully. Each time the either of the databases are opened the machine then has to reload the runtime parameters.

 

[Pat Hartman]

A2007 doesn't come in two versions. It is only 32-bit and that's why it worked.

Yes. Uninstall the 64-bit version of Office (unless you have some pressing need for overly large spreadsheets) and reinstall as the 32-bit. While you are uninstalling, uninstall the A2007 runtime as well. Multiple versions of Access do not play well with each other.

Do you really mean the recently purchased program was developed with A2K or was that a typo? I don't have any databases that old. I'm going to guess that you will be able to run it but not open it in design view and modify any objects.

 

[Lee D]

Hi Pat,

Yeah, that was not a typo .... It was a system developed for one our clients, which works and tbh is something we needed to help move our business forward.

I personally run A2007 on my machine and I was able to open the A2K and show all the modules, however I haven't tried to modify anything in design view.

Many thanks for the help above. I have re-installed office, and it works fine now.

 

[Pat Hartman]

Thanks for reporting back with your results.