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.

 

[welshgasman]

There is a bug going around.
https://www.devhut.net/another-msacc...-properly-bug/

 

[CPGDeveloper]

Thanks Welshgasm. This sucks, but hopefully Microsoft will fix this soon. As I can't seem to figure out how to fix this otherwise.

 

[Joe4]

According to that article, it looks like they rolled out a fix today.
Excerpt from the link welshgasman provided:

 

[CPGDeveloper]

Yes, I saw that, although it doesn't quite seem to be live on our end atleast -- Our IT administrator says as soon as he sees it, he'll push it through...

 

[welshgasman]

Why can't you try it yourself?

 

[CPGDeveloper]

The have blocked users from installing updates here.

 

[welshgasman]

Hmm, not sure how you are meant to get them then, unless IT download them manually.
Luckily I am on 2019 , just came from 2007, so I get none of these issues.

 

[Joe4]

Hmm, not sure how you are meant to get them then, unless IT download them manually.

I work in a similar environment. Employees are not allowed to download anything from the internet themselves. All updates are pushed down by Corporate IT Security.

 

[welshgasman]

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.