|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#11
November 28th, 2009, 05:31 PM
posted to microsoft.public.access.forms
|
|||
|
|||
I want to inhibit editing of one text box based on the contentof another
Amazing how simple it seems once you know the reason!
THANK YOU VERY MUCH! Bob Linq Adams via AccessMonster.com wrote: Placing it in the AfterUpdate event of the Status control will set the AllowEdit Property as soon as the Status control has a value entered. Placing it in the Form_Current event insures that when you move from one record to another, the Property is set appropriately. For example, if you ***only*** place it in the Status_AfterUpdate event, and the value entered is "Ship Requested," the AllowEdits would be set to True. If you then move to another record, where the value of Status is something other than "Ship Requested," AllowEdits will still be set to Yes, because nothing ha been done to check the current value of Status! Having the code in the Form_Update event checks the value of Status as you move to a new record and sets AllowEdits accordingly. 
|
|
#12
November 28th, 2009, 07:33 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
I want to inhibit editing of one text box based on the content of another
Yes it is! Glad we all could help!
-- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200911/1
|
|
#13
November 29th, 2009, 04:42 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
I want to inhibit editing of one text box based on the content of another
"Douglas J. Steele" wrote in
: AllowEdits is a boolean field (i.e.: it accepts True or False). More properly, a Boolean *property*, not field. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#14
November 29th, 2009, 04:57 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
I want to inhibit editing of one text box based on the contentof another
I'm sorry, but I am confused at you answer? Does it relate to my question?
Bob David W. Fenton wrote: "Douglas J. wrote in : AllowEdits is a boolean field (i.e.: it accepts True or False). More properly, a Boolean *property*, not field.
|
|
#15
November 29th, 2009, 12:27 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
I want to inhibit editing of one text box based on the content of another
I was addressing your comment "It now works great! dispite the fact that I
still do not understand it!" David was pointing out that my termininology was sloppy. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "BobC" wrote in message ... I'm sorry, but I am confused at you answer? Does it relate to my question? Bob David W. Fenton wrote: "Douglas J. wrote in : AllowEdits is a boolean field (i.e.: it accepts True or False). More properly, a Boolean *property*, not field.
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
