Possible to trap this multi-user situation?

[EManning]

Using A2003. I've got an FE with a main form with a subform. The
subform is a mixture of bound and unbound fields. The main form is
unbound and all it has on it is a combobox to choose a patient's
name. Once the patient is chosen, the subform refreshes to show that
patient's data. The problem I'm having is that 2 or more users could
select the same patient and attempt to update the subform. If user #2
tries to update a bound field (haven't tried unbound yet) on the
subform, they get a "beep" and the "no edit" icon appears in the
record selector on the left-side. I'm trying to trap that to display
a message to them that the patient is being edited by someone else.
But I cannot seem to figure out where the error is occurring. I've
set breakpoints in the Form_Error event, but it won't trap the error.
I've set breakpoints in events for various bound fields on the subform
but I still cannot trap the error. I would like for other users to be
able to view the patient's data while another user is editing, just
not be able to edit it.

The BE mdb is set to Shared, and "Edited Record".

Thanks for any help or advice.

[Rich P]

Greetings,

In a multiuser scenario as you describe, the solution you could try is
to have the users perform the edits locally and then submit the edits to
the back end db. Make sure you have referential integrity set (Primary
keys, foreign keys, relationships between the tables). This is how you
control duplicate data entry and invalid updates/deletes. As for
performing the edits locally and then submitting the edits to the
backend - this will reduce record locking - write conflicts (dead
locking on a server db).

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[EManning]

On May 5, 10:44*am, Rich P <[e-mail]:

Greetings,

In a multiuser scenario as you describe, the solution you could try is
to have the users perform the edits locally and then submit the edits to
the back end db. *Make sure you have referential integrity set (Primary
keys, foreign keys, relationships between the tables). *This is how you
control duplicate data entry and invalid updates/deletes. *As for
performing the edits locally and then submitting the edits to the
backend - this will reduce record locking - write conflicts (dead
locking on a server db).

Rich

*** Sent via Developersdexhttp://www.developersdex.com***

*_alt.0
20KDownload

Will try. Thanks for the advice.

[Larry Linson]

"EManning" <ma**********@hotmail.comwrote

Using A2003. I've got an FE with a main form with a subform. The
subform is a mixture of bound and unbound fields. The main form is
unbound and all it has on it is a combobox to choose a patient's
name. Once the patient is chosen, the subform refreshes to show that
patient's data. The problem I'm having is that 2 or more users could
select the same patient and attempt to update the subform.

In multiuser environments, each user should have his/her own copy of the
Front End, linked to shared tables with data, in the Back End. That will
alleviate your problem... provided you use proper locking, which is
certainly possible...

Larry Linson
Microsoft Office Access

If user #2

tries to update a bound field (haven't tried unbound yet) on the
subform, they get a "beep" and the "no edit" icon appears in the
record selector on the left-side. I'm trying to trap that to display
a message to them that the patient is being edited by someone else.
But I cannot seem to figure out where the error is occurring. I've
set breakpoints in the Form_Error event, but it won't trap the error.
I've set breakpoints in events for various bound fields on the subform
but I still cannot trap the error. I would like for other users to be
able to view the patient's data while another user is editing, just
not be able to edit it.

The BE mdb is set to Shared, and "Edited Record".

Thanks for any help or advice.

[EManning]

On May 6, 1:47*am, "Larry Linson" <[e-mail]:

"EManning" <[e-mail]

Using A2003. *I've got an FE with a main form with a subform. *The
subform is a mixture of bound and unbound fields. *The main form is
unbound and all it has on it is a combobox to choose a patient's
name. *Once the patient is chosen, the subform refreshes to show that
patient's data. *The problem I'm having is that 2 or more users could
select the same patient and attempt to update the subform.

In multiuser environments, each user should have his/her own copy of the
Front End, linked to shared tables with data, in the Back End. *That will
alleviate your problem... provided you use proper locking, which is
certainly possible...

*Larry Linson
*Microsoft Office Access

If user #2

tries to update a bound field (haven't tried unbound yet) on the
subform, they get a "beep" and the "no edit" icon appears in the
record selector on the left-side. *I'm trying to trap that to display
a message to them that the patient is being edited by someone else.
But I cannot seem to figure out where the error is occurring. *I've
set breakpoints in the Form_Error event, but it won't trap the error.
I've set breakpoints in events for various bound fields on the subform
but I still cannot trap the error. *I would like for other users to be
able to view the patient's data while another user is editing, just
not be able to edit it.

The BE mdb is set to Shared, and "Edited Record".

Thanks for any help or advice.- Hide quoted text -

- Show quoted text -

Each user does have their own FE. The BE is set to Shared and "Edited
Record". Should it be set to something else?