Multi-User DB Errors

[CFW]

I have read as much as I could find here and in Tony's site as well -
being directed there from here. I have a three user database with a
BE .mdb (Access 2K) in a share on one PC and each user with a copy of
the same FE on their PCs.

I have pessimistic locks enabled via the Record Locks property on the
main form. This seems to work OK but the users are getting frequent
"Cannot execute the command" errors which occur because a ######### or
DELETED row seems to turn up in the BE. The users claim to be using
the record selector on the main form or subforms if it's a subform
record delete, and pressing the DELETE key and following that with a
Save Record action I put on a command button.

Is there a BEST PRACTICE to prevent as many errors as possible when
sharing the BE? I don't care if I have to lock it down so only ONE
user can edit at a time but I'm still getting other issues. TIA

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've found that Optimistic locking works fine for all projects I've
ever worked on (greatest number of users ~150 [that doesn't mean all
were on at the same time]).

Q: Why would you have a user save a record after they've deleted a
dependent record? When the user clicks on the Record Selector of a
subform the main form's record is automatically saved (if any changes
were made). When the subform's record is deleted there is no need to
Save anything on the subform 'cuz the records gone.

The -DELETED- record display only occurs on records when someone else
deletes a record "you" are looking at. This is not a problem, unless
the user wanted to make changes to the record that got deleted, and
that would be a Business Rule problem (more like an office procedure).

In offices I've worked each person who has access to the database
usually only looks at specific records (their area of concern). The
only people who looked at all records were managers (and even they
were sometimes restricted to certain "regions" of data). Managers
usually did not mess around w/ data w/o informing the concerned data
entry op, who handled that specific data, that they were going to do
something. More often the manager just told the DE op to "do
something" to the records. This communication (office procedure)
alleviated a lot of suprises for the DE ops.

HTH,

MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQADjkIechKqOuFEgEQJaQACdEiPV6nhieK3Z7aaV4itaJP yc4EwAoKp0
4+HfxJ1frgLr0sP/bAAINNMT
=z0sj
-----END PGP SIGNATURE-----
CFW wrote:

I have read as much as I could find here and in Tony's site as well -
being directed there from here. I have a three user database with a
BE .mdb (Access 2K) in a share on one PC and each user with a copy of
the same FE on their PCs.

I have pessimistic locks enabled via the Record Locks property on the
main form. This seems to work OK but the users are getting frequent
"Cannot execute the command" errors which occur because a ######### or
DELETED row seems to turn up in the BE. The users claim to be using
the record selector on the main form or subforms if it's a subform
record delete, and pressing the DELETE key and following that with a
Save Record action I put on a command button.

Is there a BEST PRACTICE to prevent as many errors as possible when
sharing the BE? I don't care if I have to lock it down so only ONE
user can edit at a time but I'm still getting other issues. TIA