Weird Error Message

[Steve Voorhees]

I have an Access Database that I am running over a Novell Network. It has
been working fine, without any errors or problems.
This past Saturday, our IT department replaced one of the Novell servers
(GB). When a couple of the users for the database attempted to use
simultaneously today, the second user encountered an error message, which I
have been unable to find any answers to.
The message is "The table 'MSysAccessStorage' is already opened exclusively
by another user, or it is already open through the user interface and cannot
be manipulated programmatically."
Does anyone know what this means, and how to correct it? I tested it myself
this evening by opening the database on one computer, then loading it on
mine, and I did not see the error.
Any help, thoughts, or suggestions would be GREATLY appreciated.

 

[Steve Voorhees]

I believe that I have found the issue that is causing this. I found it in
the Microsoft Knowledgebase, Article ID 810415 - Database bloat is not
stopped by compacting database with Access 2002 format.
According to the article, the symptom: "If you have a database this is in
Access 2002 format, database bloat occurs when you repeatedly add or remove
large numbers of objects that contain code. You cannot stop the database
bloat when you compact the database."
The cause: "Records are added to the MSysAccessStorage system when objects
that contain code are created and the project is then compiled. Some of these
records remain when the objects are deleted. These records are not removed
when the database is later compacted."
I have followed one of their methods for the workaround, which is "If
possible, develop the database by using Access 2000 format. Then, when the
database is ready to deply, create a new Access 2002 format database and
import all the objects from the Access 2000 format development database to
the new Access 2002 database." but when I attempt to create an MDE database
file, I receive an error that states that Access was unable to create the MDE
file.
Any suggestions?

 

[Steve Voorhees]

Problem resolved. I kept forgetting to go into the code and compile the VB.