Problems when installing DB on Server on network

[Jim Normile]

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

 

[John Spencer (MVP)]

And perhaps the problems are due to corruption. You really need to split the
database and give each user a copy of the frontend linked to the backend data.

As to the currently existing problem(s).

Try creating a new blank database and importing everything into it. This may
take care of any corruption that is extant.

 

[Rick]

I would also check the permissions on your F drive. If
your users don't have Read/Write/Create/Execute, this
would cause the database to behaive in a strange manner.
I have had databases where some individuals couldn't even
see the form fields when they pulled up the form but
others worked with the database without error. Make sure
they have all of the rights except for "Full Control."

Rick