>>In fact 2 workstations had these types of errors today saying that a table was corrupted and must be fixed before opening again, however this file is not corrupt it opens just fine on other machines.

Ah, if you're using VFP8 there is a new integrity checker that reads the file hreader and sees if the number of records in the file matches the header.
If you just happen to catch it wrong while someone else is updating the file) then you get a false warning that it is corrupted.
The files won't be reported with a problem from any other VFP version because it was new in 8.

There is a bug in VFP 7 that if there is a header/table mismatch and you're writing in a transaction the data doesn't get written but not error is returned. So knowing there is a mismatch is very useful :)

Look at SET TABLEVALIDATE TO and try non-default values.
0 turns it off, and you may be able to live with that.