Jurgen Welz
jwelz at hotmail.com
Wed Jan 14 10:32:07 CST 2015
The NotInList event does not fire if you've set the limit to list property to No. Put a break (F9 key on the code line defining the Sub procedure) on the ones where you think the code is running. Your description tells me that, because you have set the limit to list to No on the other combos, the data is simply going into the table and is available next time you open the form. The reason it's going in is not due to the running of some code. It's not running anywhere. In the combo you are having problems with, the bound field is not the first visible field hence the error you're not getting with the others that simply allow the data to be added without the NIL firing. What the not in list event does is use the error as a trigger to run some code and return Access a constant that tells it to ignore the error, "Response = acDataErrContinue" Ciao Jürgen Welz Edmonton, Alberta > From: rockysmolin at bchacc.com > To: accessd at databaseadvisors.com > Date: Wed, 14 Jan 2015 07:04:24 -0800 > Subject: Re: [AccessD] Not In List Event Not Triggering > > Something IS different Charlotte but I'll be dipped if I can find it. The > combo is bound. And the value entered becomes part of the combo box list > when the form is reopened and the combo box is requeried. The requery is at > the end of the NIL event in all those procedures. So they work just dandy. > > R > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust > Sent: Wednesday, January 14, 2015 6:14 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Not In List Event Not Triggering > > It appears the Not In List event is firing properly, so check any even > slight differences between this combobox and the others. Is it bound or > unbound? Is another event interfering? I know you said the others were set > up the same way, but obviously something is different. > > Charlotte > On Jan 13, 2015 2:46 PM, "Rocky Smolin" <rockysmolin at bchacc.com> wrote: > > > Dear List: > > > > This one's got me stumped. A combo box has a not in list event. > > Entering a value not in the list does NOT trigger the event. > > > > The field before this one is also a combo box with a Not In List event. > > It's working perfectly. > > > > I can't see ANY difference between the two but there must be something. > > > > I did a decompile just to cover that option. No cigar. > > > > Any idea - no matter how outlier - is welcomed. > > > > MTIA > > > > Rocky > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com