>Hello all,
>We are distributing a VFP6 application and have found on one network configuration a problem in the corruption of FPT files. Their network consists of a peer to peer WIN98 server and 4 WIN2000 workstations. The WIN98 server is also used quite extensively as a workstation but holds all files relating to the application. Could it be that their WIN98 machine is just not fast enough to service 4 win2000 workstations? It's writing garbage into the memo fields of a central database causing a total corruption of the FPT. We are using table buffering with the corresponding tableupdate()'s but the problem is continuous. Any suggestions on similar situations are greatly appreciated.
>
>Thanx,
>Randy W. Fogg


We have seen corrupt FPT caused by:

1 The Users PC losing Power in the middle of an update.

2 The user themselves running a program that cuased the blue screen of death.


3 The server having bad disk blocks (hard drive starting to go) where the data for the table resided.


FPT files are a weak link and sometimes very hard to pin down where corrupton is originating.

HTH