Error message after installing on network

[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
..

 

[Gary Miller]

Jim,

You would do yourself a big favor if you did split the
database as running the whole thing over the network is
asking for corruption problems even if you don't have many
users. Both of your problems may be an indicator of some of
this.

The buttons that the Wizard creates do contain code that is
created and that lives in the code module of the form. You
can view this if you go to a button's event properties and
click on the grey side bar on the right side where you see
the [Event Procedure]. You could also be having problems if
it tries to Compact when one user exits and another still
has the program open.

The table 'MSysAccessObjects' is a system table that Access
itself builds. You can see these if you go to Tools/Options
and check the view system objects checkbox. I am not
familiar with the 'TempMSysAccessObjects', but it sounds
like something that Access is doing maybe in the
Compact/Repair process. You could try deleting it yourself
and see if Access will let you. If you can't get the db to
Compact/Repair, try importing all of you datase objects into
a new blank database and see if you can now do your
Compact/Repair.

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________

 

[Sandra Daigle]

Hi Jim,

Your question has already been answered in the following newsgroups:

microsoft.public.access.gettingstarted
microsoft.public.access.tablesdesign

If you feel you need to post to more than one group please cross-post (send
the one message to all groups at once), rather than multi-post (send
individual messages to each group). In this way, all responses to your post
will be available together, regardless of what group the responder was in,
and the rest of us won't have to read your post multiple times.

See http://www.mvps.org/access/netiquette.htm for more information.