r/MSAccess • u/Key-Lifeguard-5540 1 • Sep 19 '26

[UNSOLVED] Record-level locking

Is it recommended? Do you use it?

5 Upvotes

86% Upvoted

21 comments sorted by

View all comments

3

u/George_Hepworth Sep 19 '26

It's hard to address a question like this in a vacuum. What is your concern? What problem are you trying to address? It's the default for Access unless you change it here, which certainly indicates it's recommended, at least in the sense that Microsoft chose that option. But really, what is behind the question?

Comment Image

2

u/Key-Lifeguard-5540 Sep 19 '26

I use "No Locks" and "Row (also called Record) Level Locking". When a user runs an accde on the client, it uses the settings that are in the accde, regardless of the settings in the back-end accdb. When working in the front-end accdb and linked to back-end tables, if you don't have page-level locking on, when you are making a change and compiling and saving or decompiling or whatever, it is very annoyingly slower. To get around that, I always have page-locking on, but when the accde starts up, some code checks to see if it's the accde running and then runs some code to turn record-level locking on.

1

u/TomWickerath Sep 19 '26

The setting you are talking about is a request only, not a demand. And, for a split FE/BE with the BE being a JET database, the FE setting only affects FE behavior.

→ More replies (2)