Problem when converting database to accde (1 Viewer)

mo7med

New member
Local time
Today, 19:52
Joined
Feb 27, 2011
Messages
3
Hello

I have a program to work on it and the problem is that the client has several devices and each device working on the copy of Office 2010 is different 32bit and 64bit version

When converting the database to accde on a device installed on it 32bit Office does not work on the machine installed on it 64bit

And vice versa

When converting the database to accde on a machine installed on it 64bit Office does not work on the machine installed on it 32bit

I tried the solutions presented here in the forum as well as the solutions offered on the Internet in foreign sites, but unfortunately all the solutions did not pump

The secret behind it is to convert the database into accde

If there is no conversion, there is no problem

is there a solution ?
 

theDBguy

I’m here to help
Staff member
Local time
Today, 09:52
Joined
Oct 29, 2018
Messages
21,467
Hi. Compiling the ACCDB into ACCDE means removing the human readable code and converting it into computer-only readable code. Unfortunately, a machine with 32-bit Access does not know how to read code compiled from a machine with 64-bit Access because those two are basically different languages. So, the only solution is to compile two versions of your ACCDB. One 32 and another 64-bit. Then, distribute the appropriate version based on which computer is supposed to run it.
 
Last edited:

mo7med

New member
Local time
Today, 19:52
Joined
Feb 27, 2011
Messages
3
Thank you theDBguy
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 11:52
Joined
Feb 28, 2001
Messages
27,171
There IS another solution but it requires cooperation of management.

First things first: Access 32-bit WILL run on a Windows 64-bit system. The SVCHost process acts as a "shell" for software that needs a "watchdog" to handle the few inconsistencies that occur between a 32-bit environment and a 64-bit environment.

Other than a very few special cases, there are no practical differences between the operation of 32-bit or 64-bit Office components. IF you have million-row spreadsheets, then you need Excel 64-bit. Neither Word nor PowerPoint nor Access change significantly for the 64-bit versions. Therefore, if your 64-bit machine's users don't need the 64-bit version of Excel, you COULD ask your management if they would object to having the 64-bit systems downsize their Office installation to the 32-bit versions. If you do that, you have no trouble at all on a 64-bit machine. It is only the MS Office libraries that give you fits regarding the "bitness" of the app vs. the libraries.

Better news: IF you installed Office using a site license, the same license generally covers BOTH versions of Office - 32-bit and 64-bit. So it is not a license violation to switch from one to the other.

Now if you downloaded Office via something like Office 365, that might be an issue. But your first post made it clear you were using Office 2010, which does NOT have that issue. So it might be worth the headache to down-convert the 64-bit versions to 32-bit, after which everyone would only need the one (32-bit) copy of the app.
 

Users who are viewing this thread

Top Bottom