combo behaviour

[matt beamish]

I have a question regarding combo-box behaviour which is limited to a selected set of records based on a query of a bigger record set. If I click the dropdown arrow and type, the combo behaves fine. But if just start typing values, an unknown/recognised and not-in-list value appears (9.90990)

Screenshot of behaviour attached.



Can anyone enlighten me on this. I would like users to be able to type values in, but they do need to be limited to the values in the query behind the combo.

Thanks in advance.

Matt

 

[Rich]

Use the NotInList event

 

[matt beamish]

Thanks Rich, but how would I use that? What action am I trying to enforce (in code terms). I dont want to add new values to the combo list, only allow the user to start choosing by typing into the box without first having to drop the combo down.

Reading a little more, I wonder if the macros that are set to run on an update/change to the field are causing the combo to stutter and behave in such a way.

Thanks

Matt