To Steve Schapel, another question?

From: Turner (anonymous_at_discussions.microsoft.com)
Date: 05/30/04 

Date: Sun, 30 May 2004 15:49:49 -0700

You can reset the properties on the forms using the "On
Current" event. This event fires each time you move to a
new record. Check out "Order of Events" in the Help file.

Good Luck!

>-----Original Message-----
>Thanks Steve, I see how to fix that problem. Now for
>another related issue-
>If the user hits the EDIT button, this sets the
>AllowEdits YES, and turns the screen red. Now what I
>have discovered is that unless you actually change
>something in the record there is no update, therefore
the
>switch isn't reset again to NO by the proc in
>AfterUpdate. So for instance if you hit the EDIT button,
>then move to another record, you are still in the EDIT
>mode. This also happens if you move to a different tab
on
>the form.
>What I am trying to achieve is a method where each
record
>can only be edited one at a time, and only by a
conscious
>effort with the EDIT button, with fail safes if you move
>from record to record. We are a charity and our office
>staff and volunteers have very limited knowledge of
>databases. I have had many problems maintaining the
>integrity of the tables because they type into the wrong
>fields or forget the procedures when using Find, and
type
>over the existing data.
>Thanks so much for your help,
>Sandra
>.
>