Combobox + form wizard

  • Thread starter Thread starter Amy Blankenship
  • Start date Start date
A

Amy Blankenship

I was making a form starting with the form wizard today, and I found that in
one place it automatically created a Combobox for me. Normally I delete the
text box created and replace it with a combobox when I need one, but this
time Access somehow knew to put a combobox there. I've reviewed the
properties of the field in the table and the relationship in the
relationship window, and I am not seeing anything that would cause this, but
I'd like for it to happen again--it would save loads of time.

What can I do to get Access to do this whenever I have an ID field that's a
foreign key to another table that has the description?

TIA;

Amy
 
Amy,

When you establish a field as a combo box in the table properties, with 1
bound column and a column count of 2, Access reads it as a combo and
automatically sets up the combo box when you use the form wizzard. This does
save time, but what I don't like about it is how Access names the fields.
But, you can always go through your form later and change the names to fit
your naming convention.
 
But I didn't do that in this case, as I've always been told you shouldn't
use lookup fields...

-Amy
 
Interesting! I haven't heard that lookup fields are bad. I use them all the
time to constrain values and never have a problem with them. But, you say
that in this case you did not set the field properties to a combo box, yet
the wizard created the combo box automatically?

Somewhere in there you must have set some aspect of the field such that
Access read it as a look up. What I can say difinitively is that is you
establish field properties as a look up, the form wizard will automatically
create combo boxes.
 
Back
Top