SErgey,

You are right, I stand corrected.

JimB
>>>>Yes but the reasoin it is still a,.limt on VFP table sis the lock offset that VFP uses which is a 32 byte integer from the actual location so if a vfp table grew beyond the 2 gb barrier then the lock on record one could be hitting the location of another record in the table. When the tables are kept below 2 gb then the locking offset can never hit another record in the table becuase the table cannot grow to size big enough to allow that.
>>>>
>>>>This is not a guess on my part but information I learned from the VFP developers.
>>>
>>>How does this affect the memo file? I assume the record lock needs to be placed only once for each record (that is, for the DBF).
>>>
>>>Hilmar.
>>
>>Hilamr,
>>
>>That is correct I think. I don't how the memo file is handled if it is, because the memo contents can be scattered all over the file and is not necessarily in one place.
>
>The memo contents of a single record is always stored in the sequetional blocks in the memo file. That's what causes "memo bloat" because the whole memo for the record has to be written to the new place in the memo file when there is no more room in the existent blocks.