FPT ERRORS

[dave]

We are using vfp8 SP2

Occasionally we are getting errors that say the the FPT file of a particular
table is either corrupt invalid or missing. This table is written to often,
as it stores the positions of forms for each user on the network.
My question is, when a record is locked for writing, is the whole fpt file
locked or just part of it. We do not lock it with rlock() as there should
only ever be one person writing to their own position record.
Do we need to increase the setting of reprocess to avoid this problem
(Currently set to 1).

TIA Dave

[Dan Freeman]

What is SET TABLEVALIDATE?

There is no such thing as "locking a memo field", BTW. You can lock either
the current record (rlock()) or the table header (flock()). ANYTHING that
writes to the current record will cause some kind of lock implicitly, but it
will one of the two I just mentioned.

Dan

[MikeA]

Ideally you should always lock the record as it's good practice. Otherwise,
you could even inadvertanly have the record locked in a private datasession
on the same machine. Assuming, it's not a programming error, here are a few
things to look at because I also recently had that problem very bad where it
was happening every day. My issue was due to the fact that my client was
using a Win 98 server with 98 and XP workstations. But, here are some
things to check:

1. Erase the resouce files on all the computers (the foxuser files).
2. Check for bad cables, connectors or a bad network card. Not likely if
it is only an fpt that is getting corrupted but it is possible.
3. How big are the fpt files? It could be a bad hard drive (again, not
likely but possible. Check with Scandisk).
4. Duplicate fpt or cdx filename in another path or directory.

I credit Roger Ansell for this:
http://support.microsoft.com/kb/264867
http://support.microsoft.com/?id=812696

And finally check this thread I started for more info:

http://groups.google.com/group/microsoft.public.fox.programmer.exchange/browse_thread/thread/b08c7f27b1e21d7/7d2e6bda4fe0786f?lnk=st&q=%22memo+files+keep+getting%22&rnum=1#7d2e6bda4fe0786f

Mike

"dave" <da...@somewhere.com> wrote in message
news:OXpjmphw...@TK2MSFTNGP06.phx.gbl...