Do you use Stonefield Database Toolkit? Of it many nice features is the ability to fix table header problems. One of these occurs when the records are written to the table, but the count of records (RECCOUNT), which is maintained in the table header, does not get updated. So, you may physically have 100 records in your table, but the table thinks it only has 90.

Also, there have been posts within the last month or so in this forum about class libraries being corrupted on BSOD.

>We are experiencing missing records following BSOD on a Windows 2K Server with Terminal Services. Sometimes we lose 1000's of records and several days of information. Data loss is consistently on one main table (heavily used for lookups, etc.) approximately 260mb in size. No corruption, just missing records from the last entered items. (we must rebuild indexes after this occurs) Other tables are fine, no data loss.
>
>Environment is W2K Server (noSP), on Compaq Proliant 6500 quad PPRO200 1meg processors, 1.2gig memory, SMART 3200 Raid controller (write caching disabled to try to minimize any potential for problems there) 3x 10,000rpm disks. No other data appears missing, just foxpro VS6 SP3. Foxpro is used exclusively on this W2K Terminal Services computer. (for stability reasons) All hardware has had recent diagnostics and checks out fine.
>
>We never experience data loss with a 'planned' shutdown. Any ideas? All are appreciated.