Forum Discussion
How to convert Access 32 Bit Database to Access 64 Bit Database
How to convert 32 Database created with Access 2007 32 bit to Access 2016 64 bit? Manoj Kumar
Just 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.
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.
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.
https://www.devhut.net/2017/04/13/access-x32-vs-x64-compatibility/
But basically as explained by George and others, you can't do anything with the accde. It is compiled in 32-bit and is only good for running on 32-bit. You need to go back to the accdb file, address/fix any ActiveX controls, reference libraries, APIs, ... To their 64-bit equivalents and then recompile a new 64-bit accde and distribute that to your users. Everything depends on the complexity of your database.
As stated by others, if just stick with 32-bit unless there is a genuine reason to switch. In 99% of case, there is no benefit! If you use ActiveX controls, there may not even be a 64-bit version available and then you have to find another alternative altogether- You may like to review
https://www.devhut.net/2017/04/13/access-x32-vs-x64-compatibility/
But basically as explained by George and others, you can't do anything with the accde. It is compiled in 32-bit and is only good for running on 32-bit. You need to go back to the accdb file, address/fix any ActiveX controls, reference libraries, APIs, ... To their 64-bit equivalents and then recompile a new 64-bit accde and distribute that to your users. Everything depends on the complexity of your database.
As stated by others, if just stick with 32-bit unless there is a genuine reason to switch. In 99% of case, there is no benefit! If you use ActiveX controls, there may not even be a 64-bit version available and then you have to find another alternative altogether.
