Multi-user issues/questions?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a couple of questions regarding operating a shared Access database.

1. Currently, we have 6 users each with a front end (FE) working on a shared
back-end. In order to make sure that users are not concurrently editing
records on a common table, we have set the back end (BE) to all locked, so
that when you attempt to open a table someone is already working on you get
an error message. However, this message does not appear until this setting
has been made on all of the FE. Is this normal? I would have thought that
the FE all would have communicated with the BE and picked up this setting.
Is this the best way to do implement this strategy or should we just set all
of the FE to all records locked and forget about messing around with the
setting on the BE?

2. When we change the locking setting in the FE to all records we've found
that the filter and sort buttons are no longer active on any of the FE tables
that you open. Why is this? Is there any way have the FE set so that a
second user will be locked out of a table that is in use, but that the
current user can sort and filter data however they like, without make a
separate sorted query?

Thanks in advance for any ideas/suggestions.

Peter
 
Peter, optimistic locking is generally the best locking strategy. Just train
your users how to respond to the conflict dialog. I do that at installation
time with every database I write. (In reality, many users never see the
dialog, but I still think they need to know.)

Hopefully each user has a separate copy of the front end? Splitting the
application, and then having all the users in the same front end is probably
the least desirable configuration.
 
Back
Top