[CF-Database] Access database on a network

["Rex A." <rex@pgrworld.com>]

We have an Access database on a file server.  When one or more people
have it open, the Admins/programmers cannot save changes to anything:
forms, queries, tables.

Right now, what I do is we have our own individual copies of the Access
MDB, and we can make changes/additions to our local copy.  At the end of
the day, when everyone's gone and is not using the MDB, we have a
meeting, and one by one update the server copy of the mdb with all our
local copies.  Tedious, but gets the job done.

How do you suggest I go about making changes to the database?  One
successful implementation we did was to use ColdFusion for the forms,
and now the MDB just holds the tables, but this was for ANOTHER access
mdb.

We have over one hundred forms and reports on the MDB so we cannot just
abandon our Access solution.  

Another problem is that the Access mdb runs SOOOOO SLOOOOOW, and one of
our admins said that it is because Access is not really a Client/Server
product.  What it does is it creates a "local instance" of the database,
so since the database is about 135MB, the whole 135MB traverses the
network from the server to the client.

So what we did was have an MDB, MDB1, that houses all the tables, and
another MDB (MDB2) that houses all the forms, and we link the tables in
MDB2 to MDB1's tables.  But we did some time runs, and it produced
minimal effect.

I'm sure that a lot of people have Access databases that are being used
by many people.  What are the best practices for this?

Thanks!

Rex A.