>>>In the dim and distant (in Omnis), we used to use INT 21H under DOS/Windows to
>>>perform byte-range locking over a portion of the file - perhaps that's what
>>>VFP is doing.
>>>
>>>>Hi Jon,
>>>>Imagine the following senario:
>>>>Client locks a record on a file-server.
>>>>Client's PC is turned off.
>>>>IMO to correctly lock a record there should be no modifications to the dbf file.
>>>>VFP has to use server's OS for this. But more or less exaclty how it is done is shrouded in mistery to me.
>>>>Hope somebody could elluminate us on this issue.
>>
>>This is a post which does not contain any information I've gained from working here: in fact, I _haven't_ gained any information on this subject by working here. I'm Support, not Product.
>>
>>With that said...
>>
>>Before working here, I heard that Fox actually locks the current location + 2G (which is the reason for the 2G limit). Is this what you're talking about up above, Robert?
>
>Maybe they will believe you, I've posted the same response in three threads (including this thread) without any response.

As I said, I'm only guessing at the OS mechanism (INT 21H) - Albert described the 2Gb business and I'd guess that 21H is applied to the shadow area: just a guess though.