"EManning" <manning_news@[EMAIL PROTECTED]
> wrote in message
news:5fb5cb88-cb13-4d41-aeb2-66cc6a1158db@[EMAIL PROTECTED]
>I posted a question on 5/5/08 asking how to trap an error caused by
> multiple users trying to access the same patient. Here's what I
> posted:
>
> "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. "
>
> Larry Linson suggested: "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... "
>
> I stated in my original posting that is how I have it set up. Each
> user has their own FE, the BE is set up as "Shared" and "Edited
> Record". Is there a better way to set this up?
>
> Thanks for any help or advice.
>
You could create a new table that contains two fields, User & PatientName.
Whenever a user selects a patient via the combobox on the main form, a
record could be added/updated in the new table. Also, the table can be
searched to see if that PatientName already exists in the new table. If it
already exists, then another User must already have the subform open, and
the subform can be opened as readonly for the current user (with a msg).
When a User closes the main form, then their record is deleted from the
new
table.
As Larry suggested, this processs seems too complicated as Access has
built-in functions to handle this cir***stance. Maybe the users merely
need
to be educated as to what the "beep" and "no edit" icon mean.
Fred Zuckerman
|
