Invalid Index Name (Access 97)

Topic

New Reply

I am supporting a database that was converted from FoxPro. It is a very simple database that has never given me problems until now. Last week it displayed the following message: ‘O:Fibero~1cables.mdb’ isn’t an index in this table. Look in the Indexes collection of the TableDef object to determine the valid index names.
This message only appeared twice on my machine last week, right after it was reported to me. I accessed the database later that day with no problem and now I can still get in without the message. The User still can’t open it without getting the error. I can look and browse, but I can’t save or look at the tables or forms. Normally, I would have scrapped this version of the file and gone back to one on a backup tape from before the crash, but the system admins let me down. They were assuring me that they were backing up the file when in fact they weren’t. I tried to create a new database and import the data, but it won’t even let me do that.

Any suggestions? If I have to go back to the Fox Pro version someone’s head will roll. I could be in big trouble.

Thanks in advance!!

Reply | Quote

Replies

I would first do a repair and compact. If that doesn’t fix it, I would open the data table in design view, then find the field that has the index. I would remove the index, save the changes, then reset it for indexing, no duplicates (if applicable), save changes. Check your security settings, if it is a secured database, so you can get to the design view. If it is a secured database, it is possible that the user is no longer joined to the proper workgroup file (.mda, or .mde). Try it again!

Reply | Quote

Thanks!!! I think it worked. At least I can view the tables now. Hopefully the user can open the file now.

Thanks for such a quick reply!!!
-Kathleen

Reply | Quote

Rather than trying to use the repair function within Access97, you should use JetComp. It is better and it allows you to repair databases that you can’t otherwise open. You can download it from the Microsoft site. Just go to Microsoft Knowledge Base and search for JetComp as a keyword.

Reply | Quote

I didn’t even know about Jetcomp until I began reading about it in the Lounge a while back. I postponed getting it down — and then, three weeks ago, got a database that had 40 corrupted records, that were impossible to delete — we couldn’t even land on them — and the regular compact repair didn’t work. So, I either pulled Jetcomp down from the web or found it on one of our utility CD’s — and, voila! the corrupted records (memo fld only) were written to an “I couldn’t do anything with this record” file, and the rest of the database brought back to “smooth”. The 40+ records were able to be re-entered easily, because all the data except the memo fields were in the “problem” table. Thank you Lounge, for making me aware of Jetcomp! I would recommend that people download it ahead of time, you’ll never know when you might need it most!
thx
Pat

Reply | Quote

It used to come with the Jet service packs but now has to be downloaded separately, at least since that last few Jet 4.0 service packs.

Reply | Quote