>Hi Peter.
>
>>Thank you, that did it, sort of. I get rid of the unnamed table, but the dbc inconsistecy error is still there.
>
>Did you do a VALIDATE DATABASE RECOVER?

>
>>my 3000 mHz system
>
>That *is* fast machine *lt;g>.
>
I wish!! Sorry just a extra 0

But I found the cause of the empty table, sort of.
Here is wht I did to remedy the problem.
Since the bad structure had alreadyinvaded all usable backup I did the following:
1) clear the data folder
2) create new .dbc
3)run a program with copies the needed tables from a backup into the current data folder with the database verb.
use ("\\nt_TREASURY\development\vcpr\data\"+mytable)
copy("\\nt_TREASURY\development\vcpr\data\"+mytable);
to (c:\development\vcpr\data\"+mytable) ;
database c:\development\vcpr\data\mydatabase
4) I open sdt explorer and go through all added tables and recreate the indexes

!!!! on the fifth or sixth table sdt comes up with a VERY persistent error dialog I missed to print out the first few just hit continue and here we go the first entry in the dbc is namesless!!!!

the only remedy after the onsloght of dialogs to pull the plug (ctl-alt-del)

By the way I have never beeb successful with gendbc, it seems to work only with small databases. I use gendbcx but that chokes on a bad dbc also.

I will redo the before-mentioned steps again and capture the first messaged if any come up.

I remember getting into these error loops before. Unfortunately, Cancel does not cancel!!

Peter