multi-user access really slows down app...

B

Brad Pears

I have an Access 2000 app (front/back end) running on a terminal server.
When one person is running the app, the speed is decent. As soon as one
other person runs this app, look out because it slows to a crawl!! The
terminal server runs other multi-user Access apps with no problems but for
some reason this one causes issues when two or more users are on the system.
Are there some things that come to mind within the app itself that I should
be checking to see why it is so slow?? I believe the speed issue is related
to actually retrieving /updating records from the database - which I have
set up as the "backend" on the same server...

What might be some of the things I should check in Access itself that might
give me an idea or may cause problems? For instance, I have it set to shared
mode obviously, no locks and "open database using row level locking is
turned on". However, in this app, the way it is set up, no one would
actually be opening the same record twice so I guess I could turn that off.
Is there a lot of overhead generated when this is turned on?

Any help would be most appreciated...
 
R

RuralGuy

I have an Access 2000 app (front/back end) running on a terminal server.
When one person is running the app, the speed is decent. As soon as one
other person runs this app, look out because it slows to a crawl!! The
terminal server runs other multi-user Access apps with no problems but for
some reason this one causes issues when two or more users are on the system.
Are there some things that come to mind within the app itself that I should
be checking to see why it is so slow?? I believe the speed issue is related
to actually retrieving /updating records from the database - which I have
set up as the "backend" on the same server...

What might be some of the things I should check in Access itself that might
give me an idea or may cause problems? For instance, I have it set to shared
mode obviously, no locks and "open database using row level locking is
turned on". However, in this app, the way it is set up, no one would
actually be opening the same record twice so I guess I could turn that off.
Is there a lot of overhead generated when this is turned on?

Any help would be most appreciated...

Gave a look here: http://www.granite.ab.ca/access/performancefaq.htm
_______________________________________________
hth - RuralGuy (RG for short)
Please post to the NewsGroup so all may benefit.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top