Lister,

That is the End-of-File marker. It sounds like you have some contending problem that is either causing the header to be updated and moving the end of the table farther out without moving the eof or a process is writing it back over the top of appended records.

What network OS are you using?

>I am working on a multiuser VFP 5 application with some fairly large dbf tables (50,000 - 1,000,000) records. About 2 to 3 times per month and seamingly at random, primary key values are being corrupted. This corruption consists of a CHR(26), Ctrl+Z, byte overwriting a byte within the primary key field. Although I have noticed the CHR(26) at various offsets within the primary key field it seems to occur preferentially in the second byte of the field. This is true for key fields of both data type Character and Integer.
>
>Has anyone had a similar experience. If anyone knows what might be causing this I would appreciate hearing from you. I've searched the Microsoft knowledge base to no avail.