MSys(tables) (2000)

Topic

New Reply

(Edited by bfxtrfcmgr on 26-Feb-03 08:42. )

In this stand-alone db the Options/General setting for ‘Compact on close’ is set to yes. This morning I closed the application (it is usually left on for days or weeks at a time) and received the message “The Table ‘TempMSysObjects’ already exists”. As far as I could tell the db did not compact. I re-opened the db in design view and discovered six new tables that were not there before:

MSysAccessObjects
MSysAccessXML
MSysACEs
MSysObjects
MSysQueries
MSysRelationships

These tables have the property of “hidden” and any attempt to remove them generates the message “The database engine could not lock table ‘MSysAccessObjects (in that case) because it is already in use by another person or process”.

Although it has been some time since I had closed the db, I can’t recall anything I might have done to create the problem. We did try to copy the db over to a laptop a few weeks ago, but I wasn’t involved in that attempt (it failed as far as I know). In any case, I can’t be certain that the db was closed (and compacted) after that attempt.

Any clues? Any help greatly appreciated!
======================================================
I just opened a new (blank) db and the same MSys(Tables) come up there too! I’ve never seen these before.

Reply | Quote

Replies

All tables whose name begins with MSys are system tables; you should never modify or delete them.

By default, you don’t see them. You can hide/unhide them by selecting Tools/Options…, View tab and (un)checking the System Objects check box. I recommend unchecking it; under normal circumstances you don’t need to see system objects.

Your database may be corrupt, but perhaps it can be repaired. Try the following:

• To be on the safe side, make a backup copy.
• Try compacting again. If you get no error message, you may be in luck.
• Otherwise, download JetComp.exe from ACC2000: Jet Compact Utility Available in Download Center. This stand-alone utility can repair some problems the built-in compact-and-repair can’t handle.
• If that doesn’t help either, create a new blank database, and try importing all objects (tables, queries, forms, …) from the problem database. Note: you shouldn’t have system objects visible when you do this, otherwise Access will try to import those too.
• Your last resort is a backup copy from before the problem occurred.
  [/list]I hope that one of these steps help.

Reply | Quote

Thanks, once again, Hans!!

1. The internal Compact and Repair failed as previously attempted.
2. Jet Comp (thanks) DID compact, but did not repair (same error with internal Compact and Repair after re-opening original db)
3. Created new db without MSys objects diplayed and imported objects from old db. Internal (Access) Compact and Repair now working!!

Thanks Again!

Reply | Quote