Does anyone know what might cause this? I have setup a few multi-user dbs for work and it seems to take forever to load a form once the db is split. I thought it might be traffic problems in the network but once a form is loaded I can change the recordsets of the form and the data loads as quick as if the db wasn't split. It's just when you first open a form, even if the frontend is on the workstation, that things take FOREVER.
Challenge with Multi-User setup
- Thread starter Rob.Mills
- Start date
Rob,
I've experienced this before.
I don't know exactly what Access is doing at Startup, but it
is intensive, especially disk activity.
We had a large (hundreds of forms, reports, queries and VBA
code) database that took an eternity to get underway. I do
know that Access does compilations at Startup (that's why
users will get invalid references) even if they are not actively
referencing those particular forms.
These may not be noticable on a local hard-drive, but run
something off of a ZIP or a network and its slow.
The only work-around that I have found is to divide-and-conquer.
Actually "split" your front-ends so that they have only the
functionality that they need OR give each user their own
local copy of the front end (if its stable).
just a few thoughts,
Wayne
I've experienced this before.
I don't know exactly what Access is doing at Startup, but it
is intensive, especially disk activity.
We had a large (hundreds of forms, reports, queries and VBA
code) database that took an eternity to get underway. I do
know that Access does compilations at Startup (that's why
users will get invalid references) even if they are not actively
referencing those particular forms.
These may not be noticable on a local hard-drive, but run
something off of a ZIP or a network and its slow.
The only work-around that I have found is to divide-and-conquer.
Actually "split" your front-ends so that they have only the
functionality that they need OR give each user their own
local copy of the front end (if its stable).
just a few thoughts,
Wayne
RichMorrison
Registered User.
- Local time
- Today, 15:12
- Joined
- Apr 24, 2002
- Messages
- 588
Rob,
I don't think that's what SammyL meant by "is Access installed locally".
If you install Access on a desktop then MSACCESS.EXE and a lot of DLLs are stored and registered on the desktop.
You can also launch an instance MSACCESS.EXE stored on a network server. If you do then MSACCESS.EXE is copied to the desktop. This takes some time.
Further, some of the DLLs used by MSACCESS are either copied to the desktop or may be "called" on the network server.
The bottom line is:
if you can afford the licenses then install full-blown Access on each desktop.
RichM
I don't think that's what SammyL meant by "is Access installed locally".
If you install Access on a desktop then MSACCESS.EXE and a lot of DLLs are stored and registered on the desktop.
You can also launch an instance MSACCESS.EXE stored on a network server. If you do then MSACCESS.EXE is copied to the desktop. This takes some time.
Further, some of the DLLs used by MSACCESS are either copied to the desktop or may be "called" on the network server.
The bottom line is:
if you can afford the licenses then install full-blown Access on each desktop.
RichM
Similar threads
