Just had an interesting thing happen this weekend that I thouht the
development team and you fellow users may want to check out.
I had an occasion to verify one of my data files. I've done it before on
other files without incident. But on this occasion I thought I had bought
the farm.
1) I selected the option "Verify Family File..." on the "File" menu item.
2) I luckily cancelled and made the backup as suggested
3) I restarted the Verify
4) In the window next I left all options checked and then clicked "Proceed"
5) It did its thing and at the very end it gave me the folowing message:
Error
Error Opening Family File.
3011: Couldn't find Object 'tblAR'.
Would you like to TRY IT AGAIN?
6) At this point my file was totally useless. It would not load at all.
After gasping for breath I remembered that I had a backup.
I restored the file and then looked at the data base by linkng to the
tables from an Access 97 database. I also did that same for another of my
Family files. Right off I noticed a difference. The file that had no
problems when a Verify was done did indeed have a a table "tblAR'. My
problem database had a table almost named that same accept that the "A" was
an "A" with an umlat.
The problem database was not a problem at all untill I did the Verify.
My work around was to create a new "empty" database. I brought up the old
"problem" database and the new "empty" one at the same time. I used the
drag and drop method to copy the entire family file from the problem DB to
the new one. After it was complete, I deleted the problem Family File and
Renamed the New one with the proper name. Now the Verify function works
just fine. I just love those backups.
I have no idea how the table name was corrupted, but all is well now.
Mike Fauber
