Hello, This is my first post, although I use this site daily to look up
things.  I have been an Access programmer for 10 years now and consider
myself somewhat proficient.

I have a multi-user access database where there is a front-end on each
of the 4 client PCs and a backend on the server.  I also run one of the
front ends on the server.  All clients have a mapped drive (including
the server to itself) to the server and the front-ends use it for
linking to the tables.

We notice that once more than one person opens the database,
performance decreases significantly.  I noticed if use the front-end
that is on the server and link the tables to the local drive (where the
backend resides) the performance is back to normal no matter how many
people are using it.  Once I link the tables back using the mapped
drive the performance is slow again.  I also bench-marked this using
the linked table manager and refreshed the links both with the local
drive and the mapped drive.  Local took a couple of seconds and mapped
took almost a minute to refresh the 6 tables.  I also could reproduce
this with another Access database running on the same server so I know
it's not the particular database

I researched this for about a week and could not find a resolution.  I
read the top performance related issues associated with MS Access and
even tried to use the persistent connection solution.

Front ends are XP pro with Access 2003 and the server is Win 2003.  It
seems like this could is an authentication performance problem with the
Access connections modifying the ldb file, but I could not find
anything relating to this.

Any help would be appreciated
Thanks
Deke