That's good information Steve, and I appreciate your recording it here.

Regarding your sudden errors in VFP8, I suspect that they have always been there but that VFP5?/6 and 7 did NOT check the header record count.

Since you mention up to 13 users can I assume that you are NOT using Win peer-to-peer for the network? And if that is correct, what network OS and SP level are you using?

I hope you'll keep in mind that VFP8, at least when TRANSACTIONS are involved (and I think always), errors on ANY INSERT INTO... or APPEND when the record count is incorrect. I **think**, for non-transactions, that you have to check the return from TABLEUPDATE() when buffering is in use to recognize the error and react. This fact may just help in isolating a specific user or a specific sequence of usage that mitigate the occurrence of the error.

As regards your out of memory situation, I can't remember anything about this so far. It might be a good idea to start a new thread on this specific one.

good luck


>Last week we had a power outage and several workstations were shutdown abruptly, however the server is on battery and was shutdown gracefully. After restarting, I had 3 corrupt tables.
>
>Prior to VFP8, I had NEVER had a corrupt table like that. I have a canned vfp product here that occassionally had a bad index (made2manage) but my custom apps never had a problem before upgrading to vfp8
>
>Yesterday, everthing on the system is running fine and a table comes up corrupted. There were no system problems at all.
>
>At any given time I have about 13 users accessing my custom app. So far, the same table has not been corrupted twice. It's been 4 different tables. Other than that, I really dont have any other clues as to what is going on.
>
>Well there is one other odd thing. After upgrading to vfp8, I am getting an "out of memory error" on one machine. I have one pc on the network that is sitting there performing table updates as needed and at timed intervals. It's running 3 different processes, 2 are as needed, 1 is at 4am. They just update tables. Twice now I have had the out of memory error. And that never happened until the upgrade.