Combo Box problem

[Dennis SMITH]

Why is my combo box in both the table and the bound form not accepting the
hand-typed value and produces a "value not an item in the list" error even
though I know for sure the value IS in the list? When I select the value
from the list it wqorks fine and goes on to the next field.... Thanks

 

['69 Camaro]

Hi, Dennis.

Why is my combo box in both the table and the bound form not accepting the
hand-typed value and produces a "value not an item in the list" error even
though I know for sure the value IS in the list?

No, the value _isn't_ in the list, because you are using a lookup field, not
the true value stored in the table. You've encountered one of the evils of
lookup fields (which are not recommended by experts, even though they look
as if they are very easy to use). For more information, please see the
following Web page:

http://www.mvps.org/access/lookupfields.htm

_Never_ put a combo box in the table's Datasheet View, only on the form or
report, because data entry should only be made in a form, never the
Datasheet View of the table.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Dennis SMITH]

Thanks for the quick reply. I have removed the lookup property from the
table's field but it still gives the same error on the form... any solution
to this please? TQ

 

[Douglas J. Steele]

Sounds as though you've set the combo box's LimitToList property to True. If
that's the case, you need to put code in its NotInList event to handle
adding the value to the source of the combo box. See
http://www.mvps.org/access/forms/frm0015.htm at "The Access Web" for an
example.

 

[Dennis SMITH]

Yes, the LimitToList property is set to TRUE on purpose, I don't want the
user to add new values (airport codes) to the table. The problem is, the
value is not being accepted by the field when typed in manually, the
autoexpand property is YES but the field does not look up values when typed
manually even though the value IS on the list. it does accept the value if
you select it from the drop-down list though... Anyone know any solution?

 

['69 Camaro]

Hi, Dennis.

I have removed the lookup property from the
table's field but it still gives the same error on the form

When a lookup field is created on a table, if that field is added to a form,
then the definition of the lookup field is copied to the form and saved, and
subsequent changes to the field in the table are not reflected in the form's
version. You need to delete that bound control on the form and recreate it.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Dennis SMITH]

Hello Gunny

I think I need help with the combo box again. The one I had problems with
before is now working fine. I have some other combo boxes on unbound forms
used for inputting values into parameter queries. The combo boxes use
queries as a row source so that users can pick an airport code from the
list.

When I type a value into the box it doesn't find it in the list even though
it is part of the list and says that there is no such value. If you open the
dropdown list and select the value from the list it works fine. Again, the
combo box is not bound to any table field now.

How can I fix it please? Thanks

Dennis

 

[Pieter Wijnen]

Turn off AutoCorrect for the ComboBoxes.
I Guess Access is spellchecking & fixing your "typos"

HTH

Pieter