Split database slow over the network

[Tardus Merula]

We have just put a new samba server on the lab premises and upgradede all
workstations to 100 MB/s, in order to avoid using 10-mile radio link, hoping
that this would enable us to operae our MsAccess based LIMS database over
the network. While a standalone version, with both program and Data folder
on the local drive (C) the application works excelently, the moment we move
the Data ( e.i. the Tables) folder to a networked drive and reestablish
links, the LIMS becomes increadibly slow, often stops operating
alltogeather, resumes, screen goes blank?.... Queries are run very slowly,
and after each query "Calculating.." message stays there forever. Adding new
entries and the results of analysis is imposible in this situation. The
largest table has appr. 18000 records.
We tried to make the Data a shared folder, to be accessed from another
machine, but the result was the same as when operating over the network.
Please let us suggest further "hacks" we should try to make it run normaly ,
split over the network
Regards, Tardus

[Bradley]

"Tardus Merula" <ta***********@msn.com> wrote in message
news:mk******************@news.siol.net

We have just put a new samba server on the lab premises and upgradede
all workstations to 100 MB/s, in order to avoid using 10-mile radio
link, hoping that this would enable us to operae our MsAccess based
LIMS database over the network. While a standalone version, with both
program and Data folder on the local drive (C) the application works
excelently, the moment we move the Data ( e.i. the Tables) folder to
a networked drive and reestablish links, the LIMS becomes increadibly
slow, often stops operating alltogeather, resumes, screen goes
blank?.... Queries are run very slowly, and after each query
"Calculating.." message stays there forever. Adding new entries and
the results of analysis is imposible in this situation. The largest
table has appr. 18000 records.
We tried to make the Data a shared folder, to be accessed from another
machine, but the result was the same as when operating over the
network. Please let us suggest further "hacks" we should try to make
it run normaly , split over the network
Regards, Tardus

What version of Access are you using?
How complex are you forms/queries?
What sort of network are you using?

There are a few things you can do... (there are more which you could
find by doing a search of previous posts).

Some are -
- turn Auto Name Correct off
- set SubDataSheet to [None] instead of [Auto] on all backend tables
- make the path of the backend database as short as possible

Also, sometimes you need to redesign your application so it gets less
data and opens less recordsets at any one time.
--
regards,

Bradley