error messages after installing on network

  • Thread starter Thread starter jim
  • Start date Start date
J

jim

I have designed a medium size (10mb) Db in Access Xp. It
holds about 3000 records in a main table and maybe 5000
associated records in other tables. The Menus are on
Forms rather than a switchboard. When I run it on my
local Pc it runs sweetly and perfectly.
I have installed it on a server (F) drive wher it is
being accessed by three or four users, who edit, add and
adjust the records. The database has not been split to a
front end/back end setup, nor has it been replicated. I
rely on the fact that it is modest in size, and doesnt
normally have heavy traffic.......expecting it to
function in the circumstances.It is also running on a
shared basis.

I have set it to compact and repair automatically as the
user exits.....
A number of problems have arisen, the two most important
being (1)that the interface between the menu forms and
the database object has completely failed on two
occasions with the message "Module not found"....I did
not place any event code in modules to activate the menu
buttons....I just connected the buttons using the wizard
from the toolbox........what is causing this???

Problem (2)
When I attempt to compact and repair either manually or
automatically, or sometimes when just closing the
database I get an error message "Table
TempMSysAccessObjects already Exists OK/Help"......This
is not a table any user created......I cannot see it, and
the DB has grown in size by maybe 4mb......The compact
and repair pprocess will not now work......What is
causing this error and how do i ELIMINATE it please???

Perhaps the problem is to do with the network or the
network configuration The network is running on Ms
Windows 2000 server

Any advice appreciated

Jim
..
 
Hi Jim,

Regarding Problem #1, I would suspect that your database has become
corrupt - this can happen to any database but it is far more likely to occur
in an unsplit database where two or more are using the database. Splitting
the database is essential in a multiuser situation regardless of the size of
the application.

How to solve this problem . . . I think we need to fix Problem #2 first then
come back to the corruption issue. Here's how to correct the problem -
first try deleting 'TempMSysAccessObjects'. This is a normally a hidden
table so follow the steps below to unhide it:

Open the database
Click Tools->Options->View
Check the box for View System Objects
Go to the database window and under tables, find and delete
TempMsysAccessObjects.
Compact the database (hopefully it will work now)
Go back to Tools->Options->View and uncheck the box for View System Objects

If this doesn't work you may need to import everything into a new database
file.

Here's a link on this issue:

PRB: "Table 'TempMSysAccessObjects' Already Exists" Error Message May Occur
While Using the Compact and Repair Database Utility
http://support.microsoft.com/default.aspx?scid=KB;EN-US;818099

Back to Problem #1, if you resorted to importing all objects into a new
database, any corruption in the mdb should be eliminated. If you didn't have
to do the import, you can first try to decompile the database. This ususally
works - start by creating a backup of the database (just in case) then check
these links for details on how to decompile. These articles are written for
Access97 but the same method works for Access2000 and Access2002. Be sure to
make a copy of your mdb before you decompile.

Http://www.mvps.org/access/bugs/bugs0008.htm
http://www.trigeminal.com/usenet/usenet004.asp
http://support.microsoft.com/default.aspx?scid=kb;[LN];279334

After you've repaired the corruption, the next step is to split the database
and distribute a copy of the frontend to each user. Also, be sure to look at
Tony Toews' website for more detail and information on how to prevent
corruption and performance issues from occuring:

http://www.granite.ab.ca/access/corruptmdbs.htm
http://www.granite.ab.ca/access/a2kslow.htm
 
Back
Top