Jim,

I would not adjust my reply at all. The whole concept of client server and disconnected data access is in direct coinflict with the concept of holding a lock at any time other than during a transaction update. Transaction locks are automatic and totally handled by the dta server. For someone new to C/S leading them to consider trying to leverage some feature of a specific backend is leading them down a path that they will most assuredly change later when they get some experience. The first change to the backend will very likely make all of the work useless as the new backend is sure to implement things differently.

Personally, I have never seen a C/S system that is using pessimistic locking schemes. Everyone I have been near is using optimistic locking schemes.

So, in answer to your question, I would not change my reply at all even if some certain backend can do it. Besides when you lock a page you very often lock more than one record and therefore prevent others from working on ajacent records.