Multi-user access app is really slow

[Gary Wright]

I have a split db with the back end on a server and the front end on
several client machines. There is supposedly a 100MB ethernet between the
two that is generally quite lightly loaded. The problem is that the
performance of my application is quite poor. It then slows even more to
about half the speed when there is more than one front-end connected to the
back-end db. After 2 users it doesn't really seem to slow down much more
however. I am using the tables in the backend as linked tables in the front
end. I have tried to optimize the data retrieved by queries and forms to be
the minimum required but I haven't found much that helps. Any pointers
where to look to speed things up? Would trying replication help? replicate
the backend on some of the more commonly used front-end machines? I have
hesitated to get into replication as it appears to be a complex topic.
Using Access 2k.

Thanks,
Gary.

[Tom van Stiphout]

On Wed, 5 Nov 2003 21:00:14 +0800, "Gary Wright"
<gw*****@pd.jaring.my> wrote:

Make sure you have referential integrity and indexes in place.
Check with groups.google.com for other suggestions.
Replication indeed is an advanced topic, and not generally recommended
to alleviate performance problems. You should be able to address them
in other ways.

-Tom.

I have a split db with the back end on a server and the front end on
several client machines. There is supposedly a 100MB ethernet between the
two that is generally quite lightly loaded. The problem is that the
performance of my application is quite poor. It then slows even more to
about half the speed when there is more than one front-end connected to the
back-end db. After 2 users it doesn't really seem to slow down much more
however. I am using the tables in the backend as linked tables in the front
end. I have tried to optimize the data retrieved by queries and forms to be
the minimum required but I haven't found much that helps. Any pointers
where to look to speed things up? Would trying replication help? replicate
the backend on some of the more commonly used front-end machines? I have
hesitated to get into replication as it appears to be a complex topic.
Using Access 2k.

Thanks,
Gary.

[Julia Baresch]

When I did my split I found using an .mde file for front-end made
performance on filters and searches very slow. I ended up using an
..mdb file for my front-end instead. This is ok for my users since
they are not likely to try changing their form designs and such.

Another suggestion would be to make sure you have good links between
the tables with referential integrity and cascading updates.

Tom van Stiphout <to*****@no.spam.cox.net> wrote in message news:<j2********************************@4ax.com>. ..

On Wed, 5 Nov 2003 21:00:14 +0800, "Gary Wright"
<gw*****@pd.jaring.my> wrote:

Make sure you have referential integrity and indexes in place.
Check with groups.google.com for other suggestions.
Replication indeed is an advanced topic, and not generally recommended
to alleviate performance problems. You should be able to address them
in other ways.

-Tom.

I have a split db with the back end on a server and the front end on
several client machines. There is supposedly a 100MB ethernet between the
two that is generally quite lightly loaded. The problem is that the
performance of my application is quite poor. It then slows even more to
about half the speed when there is more than one front-end connected to the
back-end db. After 2 users it doesn't really seem to slow down much more
however. I am using the tables in the backend as linked tables in the front
end. I have tried to optimize the data retrieved by queries and forms to be
the minimum required but I haven't found much that helps. Any pointers
where to look to speed things up? Would trying replication help? replicate
the backend on some of the more commonly used front-end machines? I have
hesitated to get into replication as it appears to be a complex topic.
Using Access 2k.

Thanks,
Gary.