After splitting the performance is 10 slower....

I got a new job, where one quite simple Access DB was placed onto the server
with shortcuts of the whole! DB being placed onto app 5 PCs.

Of course one of the first things I did, was to split the DB and have only
the backend on the server, and the frontend on the PCs with a shortcut to the
desktop.

Now the DB itself is still opening reasonalby well, but some of the forms
take up to 1 minute, whereas the same form would open within one second when
I tested it again with the whole DB back on the server.
This happens even when no one else is using it, when I am the only user.

When I enquired if it was actually possible to use a whole DB simultaneously
by several people directly from the server, (because it had never occured to
me to set up a system that way) the staff swore to me, that yes, even a whole
DB can be used simultaneously by more than one person.

It occured to me that maybe the speed of the network is not great, because
the company I am working for uses currently 3 different residential houses
adjacent to each other, so I thought the cabling might cause a problem, but
this still does not explaint why an unsplit DB should work so much faster
than a split one.

Any ideas - I'd be so greatful!
Thanks, Lara

See these websites for more info on splitting ACCESS files and performance
tips:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.allenbrowne.com/ser-01.html

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"Lara" wrote in message
...

I got a new job, where one quite simple Access DB was placed onto the
server
with shortcuts of the whole! DB being placed onto app 5 PCs.

Of course one of the first things I did, was to split the DB and have only
the backend on the server, and the frontend on the PCs with a shortcut to
the
desktop.

Now the DB itself is still opening reasonalby well, but some of the forms
take up to 1 minute, whereas the same form would open within one second
when
I tested it again with the whole DB back on the server.
This happens even when no one else is using it, when I am the only user.

When I enquired if it was actually possible to use a whole DB
simultaneously
by several people directly from the server, (because it had never occured
to
me to set up a system that way) the staff swore to me, that yes, even a
whole
DB can be used simultaneously by more than one person.

It occured to me that maybe the speed of the network is not great, because
the company I am working for uses currently 3 different residential houses
adjacent to each other, so I thought the cabling might cause a problem,
but
this still does not explaint why an unsplit DB should work so much faster
than a split one.

Any ideas - I'd be so greatful!
Thanks, Lara

I have done a few things which were suggested on those links, e.g changing
the [Auto] in the SubDatasheet to [None] and it is definitely better, but
still not as good as before, I'll just keep trying and if I find something
else, I'll post it here :-)

"Ken Snell MVP" wrote:

See these websites for more info on splitting ACCESS files and performance
tips:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.allenbrowne.com/ser-01.html

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"Lara" wrote in message
...

I got a new job, where one quite simple Access DB was placed onto the
server
with shortcuts of the whole! DB being placed onto app 5 PCs.

Of course one of the first things I did, was to split the DB and have only
the backend on the server, and the frontend on the PCs with a shortcut to
the
desktop.

Now the DB itself is still opening reasonalby well, but some of the forms
take up to 1 minute, whereas the same form would open within one second
when
I tested it again with the whole DB back on the server.
This happens even when no one else is using it, when I am the only user.

When I enquired if it was actually possible to use a whole DB
simultaneously
by several people directly from the server, (because it had never occured
to
me to set up a system that way) the staff swore to me, that yes, even a
whole
DB can be used simultaneously by more than one person.

It occured to me that maybe the speed of the network is not great, because
the company I am working for uses currently 3 different residential houses
adjacent to each other, so I thought the cabling might cause a problem,
but
this still does not explaint why an unsplit DB should work so much faster
than a split one.

Any ideas - I'd be so greatful!
Thanks, Lara

Did you try the persistent recordset method? That is one change that can
greatly speed up the performance of split databases.

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"Lara" wrote in message
news
I have done a few things which were suggested on those links, e.g changing
the [Auto] in the SubDatasheet to [None] and it is definitely better, but
still not as good as before, I'll just keep trying and if I find something
else, I'll post it here :-)

"Ken Snell MVP" wrote:

See these websites for more info on splitting ACCESS files and
performance
tips:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.allenbrowne.com/ser-01.html

--

Ken Snell
MS ACCESS MVP
http://www.accessmvp.com/KDSnell/


"Lara" wrote in message
...

I got a new job, where one quite simple Access DB was placed onto the
server
with shortcuts of the whole! DB being placed onto app 5 PCs.

Of course one of the first things I did, was to split the DB and have
only
the backend on the server, and the frontend on the PCs with a shortcut
to
the
desktop.

Now the DB itself is still opening reasonalby well, but some of the
forms
take up to 1 minute, whereas the same form would open within one second
when
I tested it again with the whole DB back on the server.
This happens even when no one else is using it, when I am the only
user.

When I enquired if it was actually possible to use a whole DB
simultaneously
by several people directly from the server, (because it had never
occured
to
me to set up a system that way) the staff swore to me, that yes, even a
whole
DB can be used simultaneously by more than one person.

It occured to me that maybe the speed of the network is not great,
because
the company I am working for uses currently 3 different residential
houses
adjacent to each other, so I thought the cabling might cause a
problem,
but
this still does not explaint why an unsplit DB should work so much
faster
than a split one.

Any ideas - I'd be so greatful!
Thanks, Lara