Software

Ask something
Discussion Locked

access into Access 97 error

0 helpful
5 replies

by p_cheatum

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an Access97 database running on a Novell 4.1 server. Twice now users have gotten the error "The Microsoft Jet Engine could not locate the MSysDB" and would not open the database. I have copied back out from backup to restore the database but this requires reinputting data. I also have one table that is showing background programming code and new tables have shown up in the database that were not there before. (MSysAces, MSysModules, MSysModules2, MSysObjects,MSysQueries and MSysyRelaltionships).What would be causing this and what do I do to resolve the issue? The developer of the database is scratching his head...

5 replies

by yatst

I have had this happen because a user doesn't exit the db properly. Like shuts down the computer without exiting. It can also happen when someone accidently deletes the database or copies it to their location.

One more possiblity. If security is not set properly on the database the last person to open it essentially owns it. I have also had this interfere with the sys objects for the database.

There is documentation on this problem in Microsoft support.

Good Luck - your not going crazy!

by p_cheatum

It is possible that a user incorrectly closed out of the database but I think it more likely that a power surge or sag probably caused this. But I have informed the users of the importance of exiting properly.

by amielzz

The cause of this is that users on the network are sharing the same system database (that's the system.mda file) this has all of the configuration settings and various internal information stored in tables for use of Access itself. It includes things like tool bar settings, etc.

If you go to the options tab and select hide system objects. The mysterious tables will disappear. Problem is that when some other user on the network selects options 'show system objects' you, and everyone else willsee the strange tables again.

It's been years ago but I believe that we solved this by making the system.mda file read only (after correcting all of the default settings of course). You should find that file in the Access application folder.

by p_cheatum

I looked on other users computers and they could not see the extra tables and code even though under Options the "system objects" was selected.

Another techie e-mailed me directly informing me of some documentation on the Microsoft site about this problem. In reading through this documentation it suggested that I create a new database and import the tables, queries, etc. into it. I did this and created new tables to replace the corrupted ones. Seems to be O.K. now.

This discussion is closed to new replies.