Morning all,
Edit: Known bug. Ignore post. Maybe useful info included re batch file launcher.
I seem to be having an issue where the ldb file remains after access closes. In some cases there is an accompanying access process and other times, there isn't.
I've read about the issues a previous version of O365 had with this, and my office is up to date Version 2408 Build 16.0.17928.20114
I've also included the FE folder in the trusted locations (C:\%userprofile%\AppData\Local\ClarityLIMS\)
I seem to be unable to add the BE network location to trusted files though, even if i tick the allow network locations. I figured this wasn't so important as long as the FE folder location is there. Although I do still get active content is blocked on any new version..
I don't seem to have this issue on any of the users still on Office 2021.
Resorted to launching the DB through a batch script that checks if an ldb file is present, kills any access processes and deletes the ldb file before launching the FE. Which is far from ideal
I *may* have released an FE to the userbase which had a ldb file associated with it. But i've also tried rolling back to earlier versions with no luck.
Any clues?
Edit: Known bug. Ignore post. Maybe useful info included re batch file launcher.
I seem to be having an issue where the ldb file remains after access closes. In some cases there is an accompanying access process and other times, there isn't.
I've read about the issues a previous version of O365 had with this, and my office is up to date Version 2408 Build 16.0.17928.20114
I've also included the FE folder in the trusted locations (C:\%userprofile%\AppData\Local\ClarityLIMS\)
I seem to be unable to add the BE network location to trusted files though, even if i tick the allow network locations. I figured this wasn't so important as long as the FE folder location is there. Although I do still get active content is blocked on any new version..
I don't seem to have this issue on any of the users still on Office 2021.
Resorted to launching the DB through a batch script that checks if an ldb file is present, kills any access processes and deletes the ldb file before launching the FE. Which is far from ideal
I *may* have released an FE to the userbase which had a ldb file associated with it. But i've also tried rolling back to earlier versions with no luck.
Any clues?
Last edited: