1 reply to this topic

[raymac46]

My son-in-law is setting up a rather large database in the cloud with Microsoft 365 SaaS. He is using Access to do this. When he tries to update a couple of tables using a macro, one change gets made, the other does not *if* it's the cloud Access database. He has a backup database on his laptop and when he runs the same macro on that both changes get made flawlessly. We ran the diagnostic warnings and we get one that the cloud database has a lock error and one of the changes won't be made.
We think there's some Internet latency problem and the first change isn't finished before the second change is called. I advised him to either put in a time delay or verify that change #1 has been made before moving to change #2. He's going to put in some sort of conditional loop to do this I think.
Anybody ever seen a situation like this where things go great offline but not online?

[Temmu]

whenever i've had network issues with access, i simply delete the ldb file.

access has an mdb file and an ldb file.
the ldb file is the lock file (lock as in record lock) and may also have to do with security
mdb is, of course, the database file itself.

if you are a programmer, all transactions should be atomic.
as i yam not, you'll have to google that.