S
Sandra
I am developing a database of donors. The input is done
using a tabbed form with 3 pages. We use volunteers that
sometimes have minimal db skills and quite often when
using Find to search for a record they get ahead of the
game and type in the field of the record rather than in
the field on the Find popup form. As a result we lose or
corrupt the original information in the fields of the
record.
I have found a solution for protecting the information in
my forms by using some event procs that open the forms
with AllowEdits/AllowDeletions false, then have an Edit
button so that the user can change information when
necessary. The forms toggle back to non-edit mode if
there is an update, the user moves to another record, or
the user switches pages.
This is working pretty good but I have one glitch that I
just can't figure out how to do. I am a VB novice so I'm
asking you gurus to advise me here PLEASE!
One of my pages is a form with 2 subforms for recording
donations. The user is moved to one of the subforms
based upon a combo box selection in the main form. The
reason behind this is that we have several categories of
donations (i.e. the combo box); most of the information
is the same for every category, but 2 of the categories
require additional information fields that can sometimes
be lengthy descriptions of in-kind donations or for names
and beneficiaries of memorials. I thought that these sub-
tables would be the best way to handle the extra fields
of information.
My problem is how to protect the records when inputing on
this form for donations. My current schema of edit mode
and non-edit mode causes a hitch in the giddup, because
when the user is moved to one of the sub-forms, the event
procs are triggered, non-edit mode is switched on, and
when the user re-enters the main form they can't complete
the data entry for the record.
I have been trying to figure out If statements like "if
you move to this form or that form don't do the non-edit
mode switch" but I am really just making a mess of things!
Can someone please give me some advice? Is there some
way to do what I want using the event procs, or is there
a better way to structure the forms and tables?
Thanks so much,
Sandra
using a tabbed form with 3 pages. We use volunteers that
sometimes have minimal db skills and quite often when
using Find to search for a record they get ahead of the
game and type in the field of the record rather than in
the field on the Find popup form. As a result we lose or
corrupt the original information in the fields of the
record.
I have found a solution for protecting the information in
my forms by using some event procs that open the forms
with AllowEdits/AllowDeletions false, then have an Edit
button so that the user can change information when
necessary. The forms toggle back to non-edit mode if
there is an update, the user moves to another record, or
the user switches pages.
This is working pretty good but I have one glitch that I
just can't figure out how to do. I am a VB novice so I'm
asking you gurus to advise me here PLEASE!
One of my pages is a form with 2 subforms for recording
donations. The user is moved to one of the subforms
based upon a combo box selection in the main form. The
reason behind this is that we have several categories of
donations (i.e. the combo box); most of the information
is the same for every category, but 2 of the categories
require additional information fields that can sometimes
be lengthy descriptions of in-kind donations or for names
and beneficiaries of memorials. I thought that these sub-
tables would be the best way to handle the extra fields
of information.
My problem is how to protect the records when inputing on
this form for donations. My current schema of edit mode
and non-edit mode causes a hitch in the giddup, because
when the user is moved to one of the sub-forms, the event
procs are triggered, non-edit mode is switched on, and
when the user re-enters the main form they can't complete
the data entry for the record.
I have been trying to figure out If statements like "if
you move to this form or that form don't do the non-edit
mode switch" but I am really just making a mess of things!
Can someone please give me some advice? Is there some
way to do what I want using the event procs, or is there
a better way to structure the forms and tables?
Thanks so much,
Sandra