>I know a couple of reasons that a table can get trashed, garbage characters instead of valid data, like a user turning off a computer without exiting the application, power outage, etc. Here's the situation...
>
>A network (Netware 4.x) VFP application with the tables on the server, workstations running Windows 95/Client32. Memo files have been trashed infrequently in the past, but recently they have been getting trashed more often. And now other fields, not memo, are starting to show up with garbage characters. We have done all of the regular trouble shooting things, FoxFix, reindexing, etc. However, it has occured again. The users have been thoroughly instructed to exit the application, no power outages have occured recently, etc.
>
>What other things can cause tables to get trashed?
>
>Thanks.
I had a client running Netware 3.12 that had a very similar problem. I wound up copying the memo file to a backup text file each time a user edited the memo (for recovery purposes) to a file with a name based on the keyfield. Just before saving it, I would erase the previous backup file. This way any previous version can be recovered as long a Netware purge was not executed.

Just a thought...after saving the record issue
=RLOCK()
UNLOCK

I'm not sure if this will help or not, but it forces the network to actually go any write to the table apparently bypassing any network caching.

Let me know if this helps at all.
//:^)