Re: Combo Box Problem
- From: Tim Ferguson <FergusonTG@xxxxxxxxxxxx>
- Date: Thu, 23 Mar 2006 11:04:14 -0800
=?Utf-8?B?QWxhbg==?= <Alan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:C4538D15-FC83-472E-B9B4-056F1409858C@xxxxxxxxxxxxx:
I don't want the users leaving
the form without seeing the second filed updated.
One disadvantage of the Form_BeforeUpdate event is that the user thinks he
has finished and then gets an error message. If you can guide him into not
making the mistake in the first place, then tempers remain cooled. I simply
_hate_ systems that let me do things wrong and then send back an error.
An alternative might be to leave the command button Disabled, and to use
the ComboBox_AfterUpdate or ComboBox_Exit event to validate its own
contents and only then set the command button to Enabled.
Just a thought,
Best wishes
Tim F
.
- Follow-Ups:
- Re: Combo Box Problem
- From: Dirk Goldgar
- Re: Combo Box Problem
- References:
- Re: Combo Box Problem
- From: Dirk Goldgar
- Re: Combo Box Problem
- Prev by Date: Re: Cycle through db tables
- Next by Date: Re: Combo Box Problem
- Previous by thread: Re: Combo Box Problem
- Next by thread: Re: Combo Box Problem
- Index(es):