Lock File Not Going Away!

[CPGDeveloper]

Hi All,

I administer an MS Access Application -- MS Access Front End/Azure SQL Server Back End. Micrisoft issued an Office update last week, and since then the lock file on my application will not go away.

In addition, I'm randomly getting error 3048 -- 'Cannot open anymore databases'. I've been able to solve this by removing any DAO Recordsets and replacing them with ADO Recordsets. But I still cannot get the lock file to disappear upon closing the application.

My understanding is that the long file will not go away if there's an open connection lingering somewhere -- this wasn't happenning as of last week, so I find it hard to believe that's the case, but if it is, is there a way to determine if there's some random connection still open. Or is something else going on? Any help would be appreciated.

 

[Joe4]

I aware of that process, but not sure how such fixes are meant to be applied. I thought automatically, but that requires the program to contact or be contacted for the update?, or one goes looking for it manually, to push out.

At my work, we got alerted that there are updates to be applied, and we are instructed to re-boot our computers, and the updates are applied as we shutdown/log back in.
It can be quite a nuisance at times, but we have to be hyper-vigilant in protecting our systems.
You read about all the hacks and security breaches every day!

 

[Micron]

So even though Access is a desktop app no one in these environments can turn off updates in a desktop app?