'<linked table name> isn't an index in this table' error in access 97database

  • Thread starter Thread starter MickBurke
  • Start date Start date
M

MickBurke

We've got a weird one. A client had his system lockup when he forcibly
rebooted it, he tried to open up their database which has the front
end DB on each of their PCs and the back end on the server.When most
of the users start the database it starts as it should and operates
just fine. When this user opens the database it gives a Runtime error
3015 and reports that "<one of the linked table names> isn't an index
in this table. Look in the indexes collection of the tabledef object
to determine the valid index names."

If I hold the SHIFT key when opening the db, and then try to open one
of the linked tables, I get teh same error without the runtime
reference at the top.

Everything I've found on this error says it's a currupted db, but the
database appears to be fine as it runs on every other system. I also
coppied the front end database from one of the other systems to make
sure it wasn't that one that had gotten currupted and that didn't
help.

Anybody have any kind of suggestiosn for this? It's the company
president's PC that is having the problem so I'm desperate for a
solution!

Thanks for any input.

Mick
 
I would suggest that you get everyone out, backup the backend, then open it
and use Tools, Compact and Repair.

That may be enough, but I'd be inclined to open the frontend, delete the
links, recreate them, Compact and Repair it. Then distribute this frontend.
It's the company
president's PC that is having the problem
Click to expand...

Ain't it always...
 
Hi Mick,

In my experience, when a database front end works fine everywhere excepting
one PC - it's usually the PC's Access installation that has gotten whacked
somehow. Running office repair might solve the problem. If you have both
Office and runtime versions of Access on the PC, then sometimes the file
associations etc can get whacked and the PC will try to use runtime for
every mdb file. The cure for this runtime power grab is to navigate to the
office folder and manually run MSAccess.exe from your C:\Program
Files\Microsoft Office\... folder. It will come up, see that it isn't
properly hooked up and reassert itself as the MDB boss.

Keep in mind that, when Access gets whacked, the text of the error message
may have nothing to do with the root cause of the failure. The error
handling tends to assume that Access is okay so it must be blah blah blah in
the database that is messed up.

Hope this helps,
Gordon
 
Back
Top