Totally random MS Access error when trying to load the FE

[baadams]

This all happened after a recent update to Office 2019.

We have a loaddb.accde file that loads the front end database to the users machine and launches it from there. When we updated to Office 2019 users couldn't open the .accde file because it was created on a 32 bit machine. So I re-created it and sure enough after that no user with a 32 bit machine could open it. So we decided to just make it a .accdb file. Problem solved. Well sort of.

If the user has a new install it doesn't trust the database. Once they get the prompt to trust the database is where the error occurs. If they don't select "Yes" within a few seconds the database goes into a loop just loading the form over and over until you can finally hit "Yes" to trust the database. After you have done that once everything works fine. So it's very hard to test the issue, because we have to find another machine each time. We don't seem to have this issue if they're using the old accde file. Not sure why they would act differently considering the code is identical.

Does anyone know why it would go into a loop? All the accdb file does is open a form to let them know the database is being copied to their computer with an on timer event of 1000. Once the event is triggered it then copies the FE to their computer opens the FE and closes loaddb.accdb. This file has worked for 10+ years, now all of a sudden it's giving us an issue.

In the event of an error, it never copies the front end to the local directory, just keeps re-opening a new loaddb.accdb file until you can finally click "Yes" to trust the database.

My only solution right now is to wait until everyone has been upgraded (who knows when that would happen) compile the accdb file on a 64 bit machine and distribute a 64 bit version of loaddb.accde

Thanks!

 

[Micron]

I'd say your answer to the loop is the timer value of one second, which was likely not an issue before the upgrades. Seems like you have multiple issues, all which probably could be solved if IT installed 32 bit Office but I bet that's a no-go even though there is little benefit in 64 bit. In fact, there are things that will run in 32 but not 64 - unfortunately I cannot remember what those are (maybe API calls). This link might help but not Trusted Location issues.

Access x32 vs x64 Compatibility | DEVelopers HUT

What to know about Access 64 bit (x64).

www.devhut.net

 

[james_lankford]

can you have every user open access, then go to file / options / trust center / trust center settings /

check the box that says "Allow trusted locations on my network (not recommended)"

then "Add New Location"
and add the network drive

if its not on the network maybe you don't even have to check the box
just add the C drive to the new Location