Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Error and subsequent data corruption
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00843819
Message ID:
00844501
Views:
21
Hi Nancy,

See if Delayed Write Failed" Error Message When You Write a File to a Server mskb #Q321733, Description of the Event ID 50 Error Message mskb#816004 and FIX: Header Corruption Causes END TRANSACTION to Discard Appended Records mskb #Q110968 are relevant to your problem.

>I have a client that has encountered a problem. One of their programmers has reported this problem to me and I am wondering if anyone has had any similar experiences and could shed some light.
>
>They have a DBC with several fairly large tables. They have a class that processes an incoming table and updates the various associated tables in this DBC.
>
>From what I understand, the user got the message ”Windows was unable to save all data for the file (datailed path …)\foxuser.dbf." (There was no indication that this file was being updated.) Followed by the message "The data has been lost. This error may be caused by a failure of your computer hardware or network connection." Foxpro was then hung and had to be terminated and restarted.
>
>When subsequent users attempted to write to this DBC, two tables were not written to. That is the Dbfs were not updated, however the cdxs had been updated as if the dbfs had functioned properly. There was no error message at this time. Finally, when a different process attempted to use these tables, an error message was generated explaining that the index file did not match the dbf.
>
>My question is whether anyone has previously encountered these problems and/or could provide any advice on how to resolve it or catch it when it does occur. The first problem is the potential hardware/network problem that did not generate an error message. (If it was a fatal message, it may not have been recorded.) The bigger problem is the second part where subsequent users thought they were successfully writing, but were not. (Unfortunately we are still using version 6.0 with latest SPs, and are trying to convert to 8.0 ASAP, but are not there yet.)
>
>Thanks much for any information you might be able to provide.
>
>-Nancy
--sb--
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform