Shared Access database slow with Access 2007/Vista client.

[kjacob_Maine]

I have a client that shares an Access MDB on a server and approximately 5
users connect to it. It was created in either Access 2003 or Access 2000.
Access does not run on the server. When we introduced a new Vista PC a few
months ago with Access 2007, it was very slow to start up, to close and to
click on information in the database. There is a warning that some features
were disabled but I have to enable them each time and the setting will not
stay. The warning does not go away. I have added the shared path to the db
in the trusted area. All of the XP / Access 2003 PC's are able to use it
without the delay. The PC is a Dell Vostro 200, Vista Business, 2GB RAM,
Intel dual core.

 

[David W. Fenton]

I have a client that shares an Access MDB on a server and
approximately 5 users connect to it. It was created in either
Access 2003 or Access 2000. Access does not run on the server.
When we introduced a new Vista PC a few months ago with Access
2007, it was very slow to start up, to close and to click on
information in the database. There is a warning that some
features were disabled but I have to enable them each time and the
setting will not stay. The warning does not go away. I have
added the shared path to the db in the trusted area. All of the
XP / Access 2003 PC's are able to use it without the delay. The
PC is a Dell Vostro 200, Vista Business, 2GB RAM, Intel dual core.

Is your application split, with the front end
(forms/queries/reports/modules/macros) stored on each individual
users' PC and only the back end data tables stored on the server?

If not, that's the first step. It is the only viable scenario for
deploying any multi-user Access application. And it always has been.