Originally Posted by
Super Mario
As far as the references is concerned, the Guid is the same for MS Access 32B and 64B. The only thing that "sometimes" change for some libraries is the version number among Office 2010, 2013, and 2016. But assuming that you find some reference libraries that have different Guid, then put then in the code and it will work just as fine. The key in the code is "On Error Resume Next", if a reference doesn't exist, the code will skip to the next statement.
I considered installing a copy of FE in each client machine, but there are too many and that will make my job of making updates very complicated and time consuming. My solution is better for my case, but a) and b) may be better for other cases.
I have not experienced database corruption by having a shared version of application in the server; but if that happens, then Compact and Repair is what you can use to fix a corrupted database.