Why can't one copy of Access find an object in a working database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a working database on a network. Several users can open the DB and
work in it without a problem. However, one copy of Access returns the error:

"The MS jet DB Engine could not find the object 'Admin'. Make sure the
object exists and that you spell its name and the path name correctly."

I've reinstalled office twice and Access alone one aditional time (so 3
Access reinstalls). If the DB is working on other machines, and reinstalling
the Access doesn't fix the problem, what could it be that is stalling
startup? ODBC?
 
The error message seems rather cryptic, but have you tried this:

Copy the file to the user's C drive or Desktop, and see if they can
open it there. If so, perhaps it's a network permissions issue.

If each user has a client file that links to a network data file, do the
same thing, bringing a copy of the data down to the desktop, relinking
the tables and try to run it.

Check the users Write permissions on the network. I'm not sure
what the error would be if they cannot create an LDB file, but who
knows, it might be causing the error you describe.

Lastly, you could search google groups. There were some hits, but
I didn't see anything that was definitive in the first few posts returned.
(watch for word wrap on the URL)

http://groups.google.com/groups?as_...1&as_maxd=16&as_maxm=12&as_maxy=2005&safe=off
 
Hello Danny,

Thanks for your reply. Tried taking the db off the network and still got
the same odd error. I double checked and come to find out all databases she
tries to open give the message. I'm strongly suspicious of the the OS or 3rd
party files, the computer had some software problems that caused other apps
to fail. Everything has been repaired except for this one last problem.

Just so you are sure, I checked permissions on the network, she has full
rights, I made a local copy, no change, reinstalled Access several times, no
change.

Any ideas on a 3rd app or associated MS files that may be corrupt on her
computer and causing this craziness??
 
Well, the google posts suggested that the system.mdw was corrupt, but
I thought that since you uninstalled and reinstalled, it would rule out that
issue. However, it wouldn't hurt to do a search of all system.mdw files on
her computer, rename them as system.xxx and replace them with a file
you know is good.

I'm thinking that, it could be, that a third party tool overwrote the system.mdw
and that the uninstall didn't remove it ... and the reinstall didn't replace it. It's
a trivial enough matter to find and replace it, and that rather does approximate
the problem being described by the message.
 
Danny,

thanks for all your help. I am going to try to uninstall Office and delete
the normal.doc file and system files. Everything else I've read suggests
this is a system, not a database, problem.

Thanks again
 
Normal.Doc sounds like a Word object. You may need to do that, but you
should definitely delete all System.MDW files, or better yet, rename them
and save the old copies, in case you might need them later.
 
Back
Top