Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Weird Corruption Problems
Message
From
31/03/2000 01:53:23
Walter Meester
HoogkarspelNetherlands
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00353042
Message ID:
00353171
Views:
15
Matthew,

>I've seen plenty of dbf corruption, but this is a new one to me and I wanted to see if anyone else had ever run into this before.
>
>I have a client who, from time to time, experiences a strange corruption in their invoice line item file. The first 2 records of the file, as well as the dbf header, are untouched. But, the next 40 - 100 records get really munged. It is not shifted data, it seems to be just overwritten. Most of the data written is unintelligible. After this corrupted section, the rest of the records through EOF are fine. The interesting thing to me is that I can see Printer Control Codes such as font names, point sizes, etc. in this corrupted block of data.
>
>It seems that some part of a print job is being written into this DBF.
>
>Hardware/Network/Software: Workstations are Pentium 166 or > with 48MB or >. Server is a NetWare 4.11 with approximately 50 users. S/W is SBT Pro Series running under VFP 5.
>
>Has anyone ever seen something like this and if so, what was causing it?

I've had this once, in a FPW 2.6a Application on a W95 workstation in a WINNT 4.0 Network, don't recall internal memory. Here I got the same problem that a part of printer output was written to a DBF. I checked the code where the print was made and couldn't discover any odd things, One question do you use the FWRITE function somewhere near the problem area ?

Anyway's after 3 times of repairing, I got sick of it and skiped the report. After that I've never seen the problem again.

In any case, it seems to have to do with the internal p-code, since there are not that much simularities in our cases. Just make some changes to your code and recompile, and hope it will never happen again.

Walter,
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform