Cant Open 64 Bit - Microsoft Access Forum


	Back to Access Forum Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

Cant Open 64 Bit

Sean Sweeney

4 years ago

I contacted my IT guy in my organization so hopefully, he will sort me out. However, I sent a front-end file to be opened on the user end. They apparently cannot open the database and says the database was created with a 64-bit version of access. Our organization just recently migrated to office 365 (from office 13). I assume we all have the same version of access. I also made sure to add the desktop (where the front-end file was located on the end-user side) as a trusted location in the trust center, just to see if that caused any issues between the initial launch of access and the modal login screen form in my database.

Is there anything else I can do on my side, as a budding "access developer" to ensure the platform I'm creating can be opened up for all of my users?

Thanks!

	Adam Schwanz @Reply 4 years ago
Not really, you pretty much just pick 32 bit or 64 bit and go with it. MOST people use 64 bit, so I build databases on that. Just make sure everyone is using the same version. You can uninstall office from the users PC that has the 32bit and reinstall the 64 bit version, you can select either or when downloading. This might be helpful. 32-bit vs. 64-bit Microsoft Office

	Adam Schwanz @Reply 4 years ago
Actually, to expand on that and make it simpler. Always use 64 bit unless you have some specific restriction that requires you to use the 32 bit.

Sean Sweeney OP @Reply

4 years ago

Thanks Adam! I'm not used to having issues with 32- vs 64-bit in a PC environment. Obviously, with iOS, this is a whole other issue; but with x86. I'm used to being able to work in both environments without issue. I guess I was hoping there would be some way to bridge it, so long as we were all in the same edition/generation of access. Still very odd considering I thought we were all on the same version. Again hopefully my IT guy will sort me out.

	Scott Axton @Reply 4 years ago
One thing to add to the discussion... Which ever you decide to use 32 or 64 make sure EVERYONE in your organization uses the same version of bit type. You don't want to be mixing them. That will create even more issues. Pick one and standardize on that type.

Sean Sweeney OP @Reply

4 years ago

Thanks for the input everyone!

a bit of a strange situation, but it was resolved. As I thought, my organization -did- update everyone to 64-bit office 365. My two primary end-users have a different install, as the three of us have full/special installs of office 365 with Access (unlike the other +30 employees in the rest of my agency, who do not require full ). Apparently, when going from Office 13 to Office 365, we had some vestigial files from the previous office install. Apparently, a 32-bit Excel Runtime was conflicting with Access for some reason and causing an issue with that one user.

I'm just glad to know it wasn't an issue, flaw, bug, or error on my end.

Dan Jackson @Reply

4 years ago

Yeah, it was fun when i first starting deploying databases out to the organisation. We all have different offices installed, 2 or 3 people had 32 bit, some didn't have access at all... I just put aside some time and checked everyones PC. While doing that, I put a folder called DB on the root of their C drive (For their Front Ends) and set that to trusted with read only access for the user. Finally set up some sync software on the server to push any updates out at the click of a button.

Long story short, its worth doing those checks once. Then its plain sailing moving forward

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Forum.

Next Unseen

New Feature: Comment Live View