Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Visual Foxpro data corruption
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00118834
Message ID:
00118848
Views:
19
Glenn,

I would look at the hardware at the client site to see if the data is being currupted due to bad sector on the disk or a bad network situation like a nic card or cable. It sounds like there is data curruption at those records.

I have seen some very large dbf and cdx files that never have the problem that you are describing.

JimB


>I have been working with Visual FoxPro 5.0 for several years as a reseller and as a programer. Our customers seem to have a very high incidence of files becoming corrupt. For example customers repeatedly get "Index Tag Not Found " errors. Our current problem is a real handful. We have a customer who backs up his data and then attempts to close a period. During the close the program crashes so he will restore his data and try again. The second time the program works fine. Even though the data was exactly the same. At first I thought that the customer was doing something silly to cause this situation, so we downloaded his complete data set and we were able to reproduce the error on our computers. The thing that complicates this situation is that the problems can appear and disappear at will.
>(Validate Database Ok Index All OK) Specifically the code:
>
>USE APCHCK
>COPY TO TEMP1 &&/// CRASHES "READ ERROR IN FILE"
>* OR
>USE APCHCK
>DO WHILE NOT EOF()
> ? CCHKNO
> */// Crashes with same error at records 981,1472,1965,2468,2951
> */// Approximately every 492 Records
> */// Repeatedly crashes then repeatedly works even though the files are identical
> SKIP
>ENDDO
>
>USE GLUNJE
>DO WHILE NOT EOF()
> ? CACCTNO
> */// Crashes at records 952,1430,1908,2387,2865,3344,3822,4300, */// 4779,5257,5735,6214
> */// Approximately every 478 Records
> */// Repeatedly crashes then repeatedly works even though the files are identical
> SKIP
>ENDDO
>I ran into a similar situation with several years ago with a bug in Clipper 87 indexes. But that error can be consistently reproduced on any computer 100% of the time. This error is intermittent. (crash,crash,work,crash,crash,crash,crash,work,work,work,work,crash,work)
>
>Any suggestions would be greatly appreciated. Thanks in advance.
Previous
Reply
Map
View

Click here to load this message in the networking platform