Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Phantom Errors In Database Container With FoxFix

Status
Not open for further replies.

ibanezGuitars

Programmer
Jul 8, 2004
22
US
Greetings and Slautations,

I'm having a problem with VFP 7 (SP1) and FoxFix 5.1.

I've had people disappearing on searches yet their record is there if I go in and look manually. I have reindexed but this does not fix the problems 100%. My database container (PreScreen.dbc) always scans cleanly with no errors of its own but there are two problems occurring.

Scanning the database container reports there are no errors in the container. But I get errors scanning certain tables which indicate there are errors in that database container Duplicate Memo pointers too - even though the table I'm scanning has no memo fields.

I went back and created a brand new project and database container and I got the same errors with the first free table I added to the container.

Your thoughts or any suggestions would be greatly appreciated.

Thanks for your time,

Dave

 
Sounds like it's the tables, not the DBC, that have problems. Have you tried fixing the tables?

Tamar
 
I had an Ibenez bass once. I loved it! But alas, no more. Stupid me, I sold it once when I was in a bind.

Anyway,
I have reindexed but this does not fix the problems 100%.
Have you tried deleting and recreating the indexes?
Reindexing can take corrupted data and index on it, whereas recreting them from scratch almost certainly guarantees a valid index.
Worst case scenario, recreate them all and import the data.
Of course this all goes without saying, but I will anyway: Be sure to have good backups.

-Dave Summers-
[cheers]
Even more Fox stuff at:
 

I went back and created a brand new project and database container and I got the same errors with the first free table I added to the container.

Before adding the tables to the container, open each of them, copy structure with
COPY STRUCTURE TO MyNewTable
then add data to it with
APPEND FROM MyOldTable

This procedure most often helps fix slightly corrupted tables, very often with no data loss.

Then, in the new table, recreate index tags from scratch, as Dave Summers suggested; this will create clean index files.

Then add the new table into your newly recreated database.
Should do it.

Of course, back up first.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top