secured split db: slower access for admin than normal user?

  • Thread starter Thread starter Glenn
  • Start date Start date
G

Glenn

I'm discovering more and more "features" of multi-user secured access.
Latest is the sluggish performance of access queries if the current user
is member of the admin group compared to normal speed if logged in by a
non-admin user.

Two users (1 admin, 1 normal) log in their own frontends linked to a
backend database (Access 2000).
At the time of login, other (normal) users are already using the
database.
At startup a unbound form opens containing a bound subform.

the normal user gets it after about 10 seconds.
the admin user has to wait 2 minutes.

The delay seems to be caused by a different completion time of the data
queries.
the same occurs if the data queries are run directly.

Could it be the admin user tries (repeatedly) to get exclusive rights on
the data ?(eventhough they are snapshot queries)

The admin user main purpose is to add/remove normal users & modify their
permissions.

regards
glenn
 
Get the admin to log in on the other user's PC & vice versa. Then you'll see
whether the problem goes with the user, or the PC. IMO you can not deduce
that from the tests that you have run so far (as described here).

HTH,
TC
 
Get the admin to log in on the other user's PC & vice versa. Then you'll see
whether the problem goes with the user, or the PC. IMO you can not deduce
that from the tests that you have run so far (as described here).

HTH,
TC
Click to expand...
8<
as far as i can make out, it is linked with the user. I've tried it on
different machines wit more or less the same problem.

I think something is wrong with the mdb file itself.
opening the mdb file with the develop.mdw also takes a long (too long)
time and that's when no one is using the db.

also, I keep getting locking problems linked to specific users and just
now again "can't update the table, currently locked" without a user
specified.
the last error could refer to an "oplocks problem on the server" (have
to look into that)
But the same time, there is another seperate Front/backend database
using the same users.mdw, working without a glitch ?!

I think I'am going to recreate the problem mdb from scrath and see it
this improves something.

bye,
glenn
 
Back
Top