B
Bruce A. Perry
I've created a custom task in which I have 10 Accept check
boxes and 10 Reject check boxes which are associated to 10
individuals titles. If any one of those 10; rejects in the
task all check boxes are Enabled = False, and an email is
sent out. I found that if I check Accept and save; that
the check does not stay in the saved item. This is a
result of the check box not being part of a userdefined
field, (or Field). When it is associated with a field the
checks stay. However when this happens I loose all
programming control over the check box launching any
actions such as a message window. Has after associating
the check box to a user defined field changed my boxes
reference to the userdefined field or has the check box
become a universal reference? Help?
boxes and 10 Reject check boxes which are associated to 10
individuals titles. If any one of those 10; rejects in the
task all check boxes are Enabled = False, and an email is
sent out. I found that if I check Accept and save; that
the check does not stay in the saved item. This is a
result of the check box not being part of a userdefined
field, (or Field). When it is associated with a field the
checks stay. However when this happens I loose all
programming control over the check box launching any
actions such as a message window. Has after associating
the check box to a user defined field changed my boxes
reference to the userdefined field or has the check box
become a universal reference? Help?