ACCESS 2007

[kcaremore]

There are several users on the server that houses the program. When two or
more are using it at once, the program slows to a crawl. What can be done
about that?

 

[Jerry Whittle]

1. Check the users' permissions. All need read, write, create, and delete
and/or modify privileges to the databases file(s) AND the entire folder that
those files are in.

2. Split the database. The Back End (BE) holds just the tables and this file
should be the only one out on the network. The Front Ends (FE) hold the
forms, queries, reports, etc., and should be on each user's computers. In
other words the forms, reports, etc., should NOT be on the network.

3. Check out Tony Toews' web page on performance problems.:
http://www.granite.ab.ca/access/performancefaq.htm

 

[kcaremore]

Jerry, One other issue we had today was that when two were in the same data
base, one saved a form she updated and it ended the other one's program.
Only one was still running.

I did a test on the split and the db did move faster, but only one could use
the back up. I tried to simulate two people using the db at the same time by
opening it twice, but I'm not sure that is an accurate test.

The forms, reports and queries were still on the shared drive after the
split. I don't understand how all of us would be able to use the forms,
reports and queries if they were not on the shared server. If they are on
each users computers, how does the updating from each user become integrated
to the table?

 

[Larry Linson]

Jerry, One other issue we had today was that when two were in the same data
base, one saved a form she updated and it ended the other one's program.
Only one was still running.

You must have exclusive use to update the design of an Access database...
this is NOT new with Access 2007. Proper procedure is for a separate
database be used for development, and when changes are made and
appropriately tested, to replace each user's "Front End" with the
development database. (Yes, this requires the database be split. Tony Toews
has an "AutoFEUpdate" at his website that many find useful.)

I did a test on the split and the db did move faster,
but only one could use the back up.

I don't understand what you mean by this statment.

The forms, reports and queries were still on the
shared drive after the split. I don't understand how
all of us would be able to use the forms,
reports and queries if they were not on the shared
server. If they are on each users computers, how
does the updating from each user become integrated
to the table?

Each user's front end is linked to the Tables in the shared back end, and
with proper locking choices, Access "understands" and handles that issue.

Larry Linson
Microsoft Office Access MVP