Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Windows Error - Delayed Write Failed
Message
From
04/02/2003 13:51:39
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00748455
Message ID:
00748987
Views:
19
That's both good (for you, anyway) and troublesome.

One person here reported getting this consistently on CDXs (well, by 'consistently' I mean that when it occurred it was always a CDX). You are sure, in your case, that it was a DBF I suppose.

It is troublesome because IN THIS CASE the error message seems to be UNwarranted (you've confirmed that all data expected got there). Does this mean that there is a problem in the OS error dectetion/processing or does it mean we've got some flaky hardware on our hands or what???

I'm sure you are concerned. The only time I've had that same message, I was running only Outlook Express and saving a Word document, and all I did was to save it elsewhere and then re-save to the desired place. But it concerned me, and these reports here concern me too.

Anyway, it IS good that your data was all there.

cheers


>Hi Jim,
>I an concerned about this , luckily in the site where it has happened, it has been in a legar 'Batch Type' intake of data and I was able to compare what should have been copied with what was copie.. and it looke ok, but I am still concerned.
>
>Regards,
>
>Gerard
>
>
>
>>Hi Gerard,
>>
>>Have you ever compared the records in the appended-to table versus the original input that you append from or the table copied versus its original?
>>
>>I can see lots of conditions in applications where they would continue to run in the absence of 'random' records. The error message certainly suggests that records WILL BE LOST.
>>
>>I know that I'd worry if/when I got that message.
>>
>>good luck
>>
>>
>>>Hi.
>>>I'm getting this error in an app when I am appending or copying a largish file (say around 30,000 records)
>>>
>>>It seems to happen at the end of the copying . If I ok it, it continues on and does not 'seem' to lose any data .
>>>
>>>It happens about 3 out of 4 times on a big file operation, but otherwise the APP seems to be fine in dat to day running.
>>>
>>>(Running Windows 2000 w/s onto Windows 2000 server, VFP6)
>>>
>>>Anybody got any ideas what this is all about.
>>>Regards,
>>>
>>>Gerard
Previous
Reply
Map
View

Click here to load this message in the networking platform