Forum Discussion
How to convert Access 32 Bit Database to Access 64 Bit Database
First, let me make clear what I'm saying. Usually an ACCDE is created to protect the design of forms, reports, and VBA codein a database application. The ACCDE may or may not contain the actual data tables -- often, it contains only links to the tables in another database (generally referred to as the "back-end", whereas the ACCDE is the "front-end").
If she has only 64-bit Access and the ACCDE was built with 32-bit Access, then she won't be able to open and run the ACCDE as an *application* -- she won't be able to run the forms and reports, and won't be able to execute any code it contains.
All I'm talking about is a way to get to the tables (if any) and queries in the ACCDE.
To do that, she would open her copy of Access without selecting an existing database. She would then tell it to create a new, blank database (not a web database). She'd have to provide a name and folder path for that database, and then click the "Create" button. Access will create the database and open it, and will probably open an intial sample table, "Table1". She should just close that table.
She should then go to the "External Data" tab on the ribbon, and from the "Import & Link" tab group she should click "Access". She'll tehn be shown a dialog prompting her to specify the source of the data. She should enter or browse to & select the ACCDE that she's interested in. She should also choose the option, "Link to the data source by creating a linked table". The she should click the OK button.
She'll then be shown a Link Tables dialog where she can select the tables to be linked. It will only show the tables that actually reside in the database she's linking to -- if the ACCDE has linked tables to a back-end somewhere, those tables won't appear. She should then select the tables she wants to link, click the OK button, and Access will take it from there.
If it turns out that the ACCDE has only linked its tables, then she can import the table links instead of linking tables. She'd follow basically the the same process but instead of choosing the "Link ..." option, she'll choose "Import ..." instead. That will copy the table *links* from the ACCDE into her working database.
If the ACCDE contains stored queries that she wants to use, she can import them. To do that, she would use a similar procedure, except that she woluld choose the "Import" option, go to the Queries tab of the Import dialog, and select the queries she wants.
- Eric1890Oct 18, 2021Copper Contributor
mustafiz salam sajib Can you build a database that works for both 32 and 64 bits?
- George_HepworthOct 18, 2021Silver Contributor
Yes, with conditional compilation it is possible. Additional reference. EXCELLENT VIDEO on 64 bit VBA. However, if your Access relational database application uses 32 bit activeX or third-party controls you can't run them under 64 bit Office. So, it does indeed depend on the specifics of the Access relational database application in question. Some will be compatible, some won't.
- Sven JohannsenOct 18, 2021Brass ContributorDepends. If you are going to just run the . mdb/accdb, yes, doesn’t matter. If you are planning to compile into an executable, no. The compiled version will look for compatible Office Libraries and they need to match. Same thing for additional Office programs. If you installed 32 bit Office, you can’t install 64 bit Visio. If you have the DB on a shared drive, you can open it in either 32or 64 bit Access. This is a pretty old thread though, so the prevalence of 32 and 64 bit Office installations may be different now.
- Eric1890Oct 18, 2021Copper ContributorThanks
- Ibrahim IdrisDec 04, 2019Copper ContributorStill give me this message:-
"This database was created with 32-bit version of Microsoft Access. Please open it with the 32-bit version of Microsoft Access." - Mohammed_S_SafiMar 30, 2019Copper Contributor
Thanks for information but I still have the same problem
- George_HepworthMar 30, 2019Silver Contributor
And which problem would that be? Are you trying to convert from a 32 bit to a 64 bit environment? If so, there are differences in the way you need to handle API calls. 32 bit ActiveX controls won't work in a 64 bit environment.
Or is the issue related to creating an accde from one or the other?
Thanks for clarifying.- Mohammed_S_SafiMar 31, 2019Copper Contributor
Hello George Hepworth
Thanks for replaying the problem is like this:
there is a file created by the author in access type of extension is .accde they created in 32 bit version,
when I try to open it in 64 bit version not work since my laptop is 64 bit
I follow the instruction that written before but it still not work
- ManojK365Mar 08, 2017Copper ContributorThanks mustafiz salam sajib for the excellent idea. I guess, this process can convert my Access 2007 32 Bit MS Access 2016 files into 64 bit files. I just tried one sample. I will work with actual files and give you feedback.
- Sven JohannsenMar 11, 2017Brass ContributorJust wanted to note that there isn't much advantage to using the 64bit version of Access, and can actually limit things, as you can't install any 32bit Office apps along side it. There is a good discussion of 32bit vs 64bit here. https://support.office.com/en-us/article/Choose-between-the-64-bit-or-32-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261?ui=en-US&rs=en-US&ad=US
It notes that only Project and Excell would really benefit from 64bit, allowing larger files. Access 64bit doesn't allow any bigger file as far as I can tell.
Certainly, if you are using 64bit Office for some other good reason, 64bit Access is a given.- lordalotSep 28, 2020Copper Contributor
Sven Johannsen
It allows larger memory use, 32bit applications are limited to 3.5GB (4GB) memory spaces in a single instance of Access. As office apps these days run as a single instance and you have say multiple large Access DB's open at the same time then that memory space is consumed rather quickly for that single process, in some cases you can work around this by spawning programs in their own memory space which will increase performance but this breaks cross linking compatibility between objects within the application as they are ran as separate process in their own memory block. The 64bit version of office allows much larger memory allocation. I know this post is old but thought I would mention it.