I dont know the "why".

But, it seem that you can legitimate the record using a simple scatter memvar/gather memvar on the suspicious record. The values remain visible all the time, not only when the field is selected.

Of course, that was not really helpfull anyway, because the record is blank all the way :-)

How do you insert the record in the table?
Which kind of buffering is in effect when inserting?
TableUpdate?
Transaction?
Application crash?

Like Sergey said, I have seen record corruption caused by faulty network or material but not in normal situations.


>Has anyone seen the following behaivor of a DBF:
>
>Brow the DBF
>Clicking into a numeric field will display a blank cell (this is normal)
>Clicking into the same field for a suspcious record and it displays 0.00 instead of blank (this is not normal, as far as I can tell)
>
>To see first hand what I'm talking about, try downloading ftp://ftp.arss.com/test.zip and browsing the test.dbf. Tooling around a browse window, you'll see that the legit records show something other than the blanked record (the record that is causing problems in my system).
>
>Ever seen this? Any idea what it is, and what would cause it?
>
>*UPDATE: HexEdit shows that the row that is different is completely filled with 00 instead of 20 like the good little records. So that kind of answers why it's different. Understanding why it occured is now the head scratcher. Anyone?
>
>Thanks in advance.
>Mike