I will be replacing the table during lunch time today. What concerns us here is that we only caught this error because of a total that was off base in a report and we are now wondering if this is happening with other tables that we don't know about.

The reason it's important is that every night we run a VFP program on a Windows2000 server to copy our FoxDOS tables onto the server. Then we use SQL DTS services to bring the data into an SQL database. Our remote offices can then query against the SQL data for information. Now that we know that the SQL data is bad because of this error (that doesn't know it's an error) in the VFP we are wondering how many other tables may be affected and if there is some way to detect when this is happening.