SQQL record locking

[twgonder]

I have a menu form that is logging jobs (collection of objects: form, query, report) run by users.
For most of it I use SQL Insert/Update/Delete via DoCmd.Execute.

I’ve started wondering what will happen when multiple users in a split database start updating the log file at the same time.
These tables don’t user Access autonumbers as the ID. I create my own primary key.

I’ve seen these pages:
https://learn.microsoft.com/en-us/of...rm.recordlocks
https://eileenslounge.com/viewtopic.php?t=9414
Lots of other videos and blogs, but I don’t see any mention of how to handle in a split db situation.

They don’t seem to apply to SQL Update, Insert, Delete, just forms or a query (which I know is an SQL, so how it’s handled remains a mystery).

Is it possible to have one SQL request attempting to write over another SQL at the same time?
Does the underlying DB engine know to finish one user’s SQL request before starting another’s SQL statement?
Is there a way to turn on pessimistic locking for SQL statements and how reliable is it?


What error situations might we have to deal with in the VBA procedures?
How about when using Set rs and rs.update?

[ranman256]

and what are the odds of 2 users editing the same record at the same time?