>>I just wondered, has anyone actually tried to overflow the 2GB limit on a Memo file ?
>>
>>I thought that the limit is about the (mapping of) locking areas onto the offset of the file(length). IOW, I don't think that locking applies to Memo files, so would it really stall something ?
>>
>>Just curious ...
>
>Peter,
>
>I do believe that locking applies to memo files. Think of replace command of a memo field over a network.
>
>Also see the help about sys(3051) and sys(3052). Memo files are clearly mentioned there

Initally agreed Gregory. However ...
Being ignorant as always, I'd say that these apply to file locking. But okay, despite one could say not to use that, there will be provisions for it within VFP. But, it could be about the header only, right ?

Furthermore, I'd say that a "record" from a Memo won't be locked directly, but all goes via the DBF's record; when that's locked, how to approach the Memo's record ?

It's my guess that some means of explicit file locking of a Memo file must exist, looking at the stupids amongst us (I would be one of them ...) who are able to attach MemoFileX to DBFFileY (where it belongs to DBFFileX). How to do that ? not sure, but possibly there are some possibilities at explicitly opening a DBF in one directory, VFP finding the Memo (not in that directory) over the Set Path.
Otherwise I wouldn't know why the Set Reprocess etc. would apply to a "Memo file".