Re: Combo Box Problem

"Tim Ferguson" <FergusonTG@xxxxxxxxxxxx> wrote in message
news:Xns978FC20102DD1garbleme4455656@xxxxxxxxxxxxx
=?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.

I agree in principle, but I don't remember that Alan mentioned any
command button, to be enabled or disabled. And there are so many ways
to save a record, I don't feel it's worth trying to handle them all.

And I _hate_ applications that force me to fill out forms in a
particular order. I may well want to jump around.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.