T
Ted
Hi.
I’m using A2K and my form is called ‘Screening Log’ and my options group is
named Frame1.
There are 7 possible conditions that can be coded in the options group
(Frame1). They basically speak to the question of ‘where’ in a potential
research project's evolutionary history any particular patient approached to
enroll in a study happens to currently be. So, e.g., Case 1 records the fact
a patient (Px) was screened, Case 2 that he/she went onto a study, Case 3 the
fact treatment (Tx) began, Case 4 that Tx ended, Case 5 that Px went ‘Off
Study’, Case 6 that Px unfortunately deceased, Case 7 that Px was lost to
follow up. Each of these conditions is associated with a control that records
the relevant/corresponding date. At this point, I'm just talking about a
record which is getting coded in a linear/chronological way.
When Case 5 is selected, it actuates a series of events which send some of
the Screening Log’s control source to another table via a macro which is
written around an append query. If the append is to be successful, the query
needs to have among other things which the user can always be counted to have
entered, the values of ‘SequenceNum’ and ‘OffStudyDate’ available to it. So
we don’t want to actually run that macro if either is unavailable. I’m
assuming that what we’re interested in doing to insure that the user is
mindful of this reality is to somehow display a message and temporarily
‘freeze’ the user from proceeding until he/she enters SequenceNum and
OffStudyDate. What we need to do is get the user’s attention and tell him/her
they overlooked the other factor(s). Also, when Case 5 is selected, I think
that we now have a selected Case5 toggle button which needs to be unselected
since when the errors corrected, the user is required to select it in order
to actuate the vba which runs the append macro.
I've tried cobbling together the code, but the part about trapping for this
error seems sort of elusive since I'm sort of new to this.
Any ideas, suggestions, etc. etc.?
Ted
I’m using A2K and my form is called ‘Screening Log’ and my options group is
named Frame1.
There are 7 possible conditions that can be coded in the options group
(Frame1). They basically speak to the question of ‘where’ in a potential
research project's evolutionary history any particular patient approached to
enroll in a study happens to currently be. So, e.g., Case 1 records the fact
a patient (Px) was screened, Case 2 that he/she went onto a study, Case 3 the
fact treatment (Tx) began, Case 4 that Tx ended, Case 5 that Px went ‘Off
Study’, Case 6 that Px unfortunately deceased, Case 7 that Px was lost to
follow up. Each of these conditions is associated with a control that records
the relevant/corresponding date. At this point, I'm just talking about a
record which is getting coded in a linear/chronological way.
When Case 5 is selected, it actuates a series of events which send some of
the Screening Log’s control source to another table via a macro which is
written around an append query. If the append is to be successful, the query
needs to have among other things which the user can always be counted to have
entered, the values of ‘SequenceNum’ and ‘OffStudyDate’ available to it. So
we don’t want to actually run that macro if either is unavailable. I’m
assuming that what we’re interested in doing to insure that the user is
mindful of this reality is to somehow display a message and temporarily
‘freeze’ the user from proceeding until he/she enters SequenceNum and
OffStudyDate. What we need to do is get the user’s attention and tell him/her
they overlooked the other factor(s). Also, when Case 5 is selected, I think
that we now have a selected Case5 toggle button which needs to be unselected
since when the errors corrected, the user is required to select it in order
to actuate the vba which runs the append macro.
I've tried cobbling together the code, but the part about trapping for this
error seems sort of elusive since I'm sort of new to this.
Any ideas, suggestions, etc. etc.?
Ted