RTE 3052, .update doesn't release a lock?

[twgonder]

Windows 11, Access 2021, Version 2407
I was just testing a little progress "bar" for inside forms,
and although I've updated hundreds of thousands of records with other code,
it seems odd that this code fails.
Just look at the two yellow highlighted lines (and the middle part) for the fundamentals of the code:



But it fails with RTE 3052 a bit over 9,000 records processed (the exact count varies).
I would have thought the ".update" would release the current record's lock. If I understand the error message correctly.
I admit I'm a bit confused with the "File sharing lock" part of the error message, why not "Record sharing lock"? I'm only updating one table. No other code is running.

Am I missing something here?
Thanks

[moke123]

The default is 9500.

You can raise it with

DAO.DBEngine.SetOption dbmaxlocksperfile,15000

[twgonder]

The default is 9500.

You can raise it with

DAO.DBEngine.SetOption dbmaxlocksperfile,15000

I'm not sure I understand exactly what we are increasing. It doesn't seem to be the locks for records that are open for editing.
The MS help doesn't tell me much.

[twgonder]

More...

The 3052 error occurs on the .Edit line, so one would think it has to do with locking the page.
I tried RecordsetOptionEnum as 1 and 3 to no affect.
Clicking on Debug, then pressing F5 allow the procedure to complete.
If there was something more than a timing problem, I would think the execution wouldn't continue.

[Welshgasman]

Would be interesting to see sAddstatus as that could contribute to your issue as you are calling it all the time?

[ano]

yeah how abt repair ur database or use a different laptop as tom van stiphout suggest

[moke123]

Here's a link

https://learn.microsoft.com/en-us/office/troubleshoot/access/file-sharing-lock-count-exceeded

[ano]

i dont believe in file share lock count exceeded bec the number is low for a database, and it will consume lots of memory in a large database i guess that tom has the right answer, special bec mentioned was it was not reaching the number but went wrong earlier but not same number

[twgonder]

Would be interesting to see sAddstatus as that could contribute to your issue as you are calling it all the time?

I've commented out the line, no difference.
There is only a dbOpenSnapshot in the called procedure, and it runs less than 200 times. It runs of thousands of times throughout the code in a session without this problem happening.
Also, I've rebooted, and the first time the procedure runs, every time after that the RTE.

[twgonder]

yeah how abt repair ur database or use a different laptop as tom van stiphout suggest

It worked once after a repair, then it fails. The next repair didn't even allow it to run once, so maybe a fluke.
I've tried on another laptop. Same problem.
Also, I've updated to 2408, problem continues.

[twgonder]

Here's a link

https://learn.microsoft.com/en-us/office/troubleshoot/access/file-sharing-lock-count-exceeded

I've read those, but they don't seem to answer what is going on. I can change it to 15000, but what happens at the next time when there´s 16,000 records?
It makes no sense for thousands of "locks" being set when were just updating one record at a time.
It talks about transactions, but I'm not doing that (i.e. .BeginTrans)

[ano]

the fact repair did once shows there is no lproblem in flow only problem in dadatbase; try create new blank database and import only what u need

[twgonder]

the fact repair did once shows there is no lproblem in flow only problem in dadatbase; try create new blank database and import only what u need

I've tried in 2 databases, one was imported. Same problem.
I'm guessing it is a cumulative problem, hence it runs fine once (with 10,000+ records), and not after.
I imagine lots of people are running similar code to do minor changes to a table field, to more than 10,000 records.
No one else is having this problem?
Again, what is the error message trying to say when we are working on one record at a time without "transaction processing"?

[Welshgasman]

Have you tried just using a query?

[twgonder]

Here, I did a simple database.
Just run the only procedure in the module.
Does it crash on other versions of Access?

TestRte3052.zip