Combo Box Errors

[Deb]

I have created several combo boxes on a form. All of them display the
appropriate selection information, but two of them are giving me error
messages:

"The value you entered isn't valid for this field. For example, you may
have entered text in a numeric field or a number that is larger than this
FieldSize setting permits."

I've gone back to the underlying tables (one for inventory storage, one as a
lookup table) and both have text fields and the field sizes in both tables
match. What am I doing wrong with these two boxes?

 

[Douglas J. Steele]

Are they bound? (is there anything in the ControlSource property?) Are you
sure that the field to which they're bound is a text field?

 

[Deb]

Yes to both questions. ControlSource contains the name of the field and in
all cases, the fields are text.

 

[Douglas J. Steele]

Not wanting to seem condescending, but are you SURE they're both text
fields? Did you possibly use the Lookup Wizard to create the field? If so,
then what the field seems to be isn't what it actually is.

 

[Deb]

Doug:
Please don't feel like you're condescending -- sometimes I feel like a
"rock".

When I created the two separate tables, I made sure I set the fields up as
text fields. I did use the Lookup Wizard to create the combo boxes, but I
did this for all of the combo boxes. Some of them seem to work perfectly,
but others give me the error message in the first post. I don't exactly know
how to set up a combo box without the wizard. Do I just do that with the
"Wizard" box unchecked?

 

[Douglas J. Steele]

The Lookup Wizard to which I was referring is the one used when creating
fields in tables, not combo boxes on forms.

If you open the table directly, do you have combo boxes in it?

 

[Deb]

No. I learned from this forum that (while all of the books I have indicate
that you can use lookup tables right within the table) that it's not a good
idea. I was advised to set the lookup fields on forms, not within the tables.

 

[Douglas J. Steele]

Sorry, nothing else occurs to me.

 

[Deb]

Thank you for your kind assistance.

One other thing did occur to me, and I don't know if it has anything to do
with this, but for some of the lookup tables, I have an autonumbering ID
primary, and it probably isn't necessary. If I remove that field and make
another field the primary, would it make any difference?

 

[Deb]

Doug:

I figured out the problem. For future reference, it was related to the
autonumber field in the underlying lookup tables. I removed the "ID"
references and set the column width for that field to "0" and the combo boxes
work like a champ!

Again, many thanks for your kind assistance!