Hi, Pete.
an error alert
comes up that says 'Table 'TempMSys Access Objects' already exists'.
First, make a backup copy of the database, just in case something goes
wrong. Now, open the database and select the Tools menu -> Options... to
open the Options dialog window. Select the "View" tab, then check the
"System objects" check box. Select the "OK" button to save your change.
In the Database Window, select the "Tables" tab. Scroll down to the
"TempMSysAccessObjects" table and delete it.
Select the Tools menu -> Options... to open the Options dialog window.
Select the "View" tab, then uncheck the "System objects" check box. Select
the "OK" button to save your change.
Select the Tools menu -> Database Utilities -> Compact and Repair Database
to compact the database. When it is finished compacting, close the database.
Attempt to open, then close, the database from across the network to
determine whether the problem has been fixed. If not, create a new database
file and import all of the objects from the original database, except the
built-in system tables (all table names starting with "MSys..."). Then, open
a module in the VB Editor and compile all code. Close the new database and
attempt to open and close the database from across the network as before.
Any ideas? Is it possible that some change may have taken place via a user
inadvertently hitting hot keys or similar?
Not unless one of the users "inadvertently" yanked the power plug or network
cable which interrupted a write-to-disk operation. Or if one of the users
Can you tell me the nature of this message?
Of course. The "TempMSysAccessObjects" table is a system table that Jet
uses while doing its housekeeping. For some reason while Jet was processing
the database, the processing was interrupted or incomplete. This table was
not deleted, but it should have been. Because this table already exists when
Jet starts to do further housekeeping, when Jet attempts to create a brand
new table with this same name, it fails. Hence, the error message.
Is it something to worry about?
I'd keep an eye on this database if I were you. It's possible that
corruption has occurred, but if it's a simple corruption, then a compact and
repair will fix it. If it's a more complex corruption, then you'll likely
find out fairly soon, because the database application either won't open or
it will act in a bizarre, unexplainable manner. If that happens, you'll have
to restore the database file from a backup.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
Beware to those who use munged addresses: known newsgroup E-mail harvesters
for spammers are (e-mail address removed) and (e-mail address removed)
- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. Remember that questions
answered the quickest are often from those who have a history of rewarding
the contributors who have taken the time to answer questions correctly.
