Make use of ACCDE much easier
Currently it is a big problem to handle ACCDE files, if your users do have different versions of Access: Full or Runtime, 2010 / 2013 / 2016, 32bit or 64bit. Please support a "low level format" with a higher level of compatibility.
Michael Gertz
shared this idea
1 comment
-
dwolovi
commented
I am familiar with the 32-bit/64-bit incompatibility. A few years ago, the tech support person for one of my clients selected the 64-bit option (for no apparent reason) when he was installing office and I had to ask that he reinstall with the 32-bit version. The issue now is, I think, much more complicated. I have confirmed that both my client and my notebook test machine have click-to-run 32-bit office installed.
My Sagekey install puts the executable in ‘C:/program data/billing’ folder. But I am now getting this message: The database is in an unrecognized format. I tried installing with 2010 SP2, 2013 (32-bit) and 2016 (32-bit) runtimes with the same result. Grasping at straws, I took a copy of the executable (accde) from my wife’s computer (which hasn’t been updated with the latest version of the app) and put it in the ‘program data/billing’ folder on my test notebook (and at my client site). The app worked fine, except, of course, it was the older version. Since I have a backup of the older version accdb, I used it to create an executable, but I got the error again when I put that accde on the notebook.
It seems to me that the problem is not with the runtime but rather with the Access upgrade that was automatically installed on my development box sometime this year. I looked online some more and found this forum:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_install-mso_win10/office-16-click-to-run-extensibility-component-64/e79ee5bd-f119-4808-9bb2-289dd815b76a
where the discussion was about “Office 16 Click-to-Run Extensibility Component 64-bit Registration prevents Office 365 32-bit installation”. If Microsoft is sticking that component on the installs (I found it on my notebook but did not try to uninstall it) then maybe that’s causing some incompatibility. But, the “old” accde didn’t have a problem. Does Microsoft even know that they have made Access unusable for general distribution?