If you have VFP you set tablevalidate to 0 and try to open the table
If you can, append an empty record, delete it, pack the table and
recreate the index.
I do that with old fox dos tables and it usually works
Rafael Copquin
El 09/11/2013 15:42, John R. Sowden escribió:
We had a computer freeze during the night (it gets cold in the SF Bay
Area), and the worker was doing data enter into a dbf using foxpro/dos
2.6, under program control. I flush the buffer after every record
entered, due to some 'segment errors' of yesteryear. Now we cannot get
back into the dbf because it comes up as a 'not a dbf' error. I have
solved this in the past but I don't remember how, and usually it was a
trial and error. I deleted the .cdx file, as I can create it easily
again. I backup this type of dbf daily, but I would rather her not
experience the re-entry process as it will reduce her confidence in
computers.
This is a header issue. What is a clear solution to this. I have hex
editors, I can write code using foxpro low level file access, etc. I
looked at the header and saw the first 16 bytes as:
03 0D 0B 09 04 19 00 00-21 01 4B 00 00 00 00 00
The file has about 6500 records (est-my daily backup wrote over the
good dbf with the bad dbf (need to rethink my daily backup program ;)
)backed up
The answer might help others with the same error.
John
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
