Hi Mike,

I've seen this happend and I believe that it's result of hardware or network failure/problem/fluke. I never was able to trace the source of such corruption and it didn't repeat again in following days. In my case it was usually more than one corrupted record and openning such table most likely resulted in FoxPro shutting down immediately.

>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