B
BruceM
I have a sort of rudimentary security system to assure that the person (who I
will call the responder) whose name appears below a text box (the response)
is actually responsible for the contents of the text box. To that end I have
a combo box from which the user selects his or her name. A hidden column in
the row source contains a password. The Before Update event for the combo
box opens a password form that includes a text box, and OK and Cancel
buttons. The OK button's click event checks the password entered in the text
box against the hidden column. If the user cannot enter the password then
neither the text nor the name will be saved.
So far so good. Sometimes the responder will need to add to the response.
My idea is that upon attempting to do so they will be prompted for the
password (using a different password form than before, if need be). After
entering the password they will be allowed to edit the response. My first
idea was that this could be in the Change event or maybe Key Up or Key Down
for the response text box, but that code seems to run at every change and
every keystroke. Got Focus would be OK, but I would rather not prevent the
user from tabbing or clicking into the text box. Whatever event I use (if I
am even on the right track with this), after entering the password into the
separate pop-up password form they will be allowed to edit the response until
after they exit from the text box. I have tried locking and unlocking the
text box (unlocking it if the password is correct and locking it After
Update, or something like that), but I cannot get all of the pieces to work
together. Any ideas? Am I attempting to reinvent the wheel here?
will call the responder) whose name appears below a text box (the response)
is actually responsible for the contents of the text box. To that end I have
a combo box from which the user selects his or her name. A hidden column in
the row source contains a password. The Before Update event for the combo
box opens a password form that includes a text box, and OK and Cancel
buttons. The OK button's click event checks the password entered in the text
box against the hidden column. If the user cannot enter the password then
neither the text nor the name will be saved.
So far so good. Sometimes the responder will need to add to the response.
My idea is that upon attempting to do so they will be prompted for the
password (using a different password form than before, if need be). After
entering the password they will be allowed to edit the response. My first
idea was that this could be in the Change event or maybe Key Up or Key Down
for the response text box, but that code seems to run at every change and
every keystroke. Got Focus would be OK, but I would rather not prevent the
user from tabbing or clicking into the text box. Whatever event I use (if I
am even on the right track with this), after entering the password into the
separate pop-up password form they will be allowed to edit the response until
after they exit from the text box. I have tried locking and unlocking the
text box (unlocking it if the password is correct and locking it After
Update, or something like that), but I cannot get all of the pieces to work
together. Any ideas? Am I attempting to reinvent the wheel here?