Using Unbound combo boxes in a form

[KristenD]

I was advised to not use combo boxes in my tables as it can cause issues. I don't want to create a table to be used for a lookup since it will only contain two bits of information.

Would it be easier to create unbound combo boxes in the form and get the information that way?

The form is based off of a table.

Thank you!

 

[boblarson]

What is your combo box intended to be used for? If you are wanting to store the selction then it would not be unbound. It would be bound to the field in the table in which you want to store the data. You would change its Row Source Type to VALUE LIST and then you can type in the two values separated by a semi-colon in the Row Source property.

 

[KristenD]

I am using it to track what type of document I have on file and there are 2 documents that I would be choosing from. I was advised in a different post not to use the lookups but I can't get away from them.

I did end up using the value list for the fields that I needed.

 

[boblarson]

I was advised in a different post not to use the lookups but I can't get away from them.

You misunderstood. The advice to not use lookups is at TABLE level, not at form level. It is perfectly good to use them at FORM level. (i.e. combo box row source gets values from a table of lookup values and the associated ID for that value gets stored by the combo into the field it is bound to.)

 

[KristenD]

Oh, so it is ok to use the combo boxes with the value list in the lookup in the design view of the table. I did misunderstand then. THank you!

 

[boblarson]

Oh, so it is ok to use the combo boxes with the value list in the lookup in the design view of the table. I did misunderstand then. THank you!

NO, NO, NO! What you just stated is what we mean at TABLE level. You don't do it in design view of the Table. You create combos on the FORM which is the lookup.

 

[KristenD]

I leave the fields in the table view as text fields then in the form change them to combo boxes doing exactly what I would at the table level but in the form instead?

 

[boblarson]

I leave the fields in the table view as text fields then in the form change them to combo boxes doing exactly what I would at the table level but in the form instead?

By George, I think you've got it.

 

[KristenD]

Thank you!! I'm slowly getting it...I definitely understand more than I did a few months ago when I began using Access and creating the program. This website has been an invaluable tool along with all the wonderful experts!

 

[KristenD]

Quick question? Is it an easy fix to go change all the tables and forms after there is a great deal of info in the database?

 

[boblarson]

Changing lookups is not a problem. In fact, here's a quick tutorial.

http://www.btabdevelopment.com/ts/removelookups

The data will still be there (albeit in the way it should be) and you would probably not need to change the forms, unless you are using value lists and the combo doesn't have them.

So it is okay to put them in at table level to help Access create your forms so you don't need to go change each of the text boxes to combos. But after you are done, you should remove them from the tables since they can cause other issues.

 

[KristenD]

They are value lists with the exception of one field.

So I can change them at the table level, then go to the form and back in the value list at the form level and this should not cause any corruption to the database with the info?

 

[boblarson]

They are value lists with the exception of one field.

So I can change them at the table level, then go to the form and back in the value list at the form level and this should not cause any corruption to the database with the info?

Nope, it will be fine.

 

[KristenD]

I created a back up of the back up of the live database so I can experiment.

Thank you again!!

 

[KristenD]

It worked!! Everything stayed the same in the forms with the combo boxes even the ones with table look ups.

Thank you thank you!!

 

[boblarson]

I created a back up of the back up of the live database so I can experiment.

Always a good idea.