Is a combo box like using a lookups?

[Eddy Sincere]

I'm designing a database which does not use lookup fields but uses combo boxes on the forms. However, I am wondering if I'm using them correctly. When I set up the combo box the row source is automatically filled with a what looks like a query statement (see Attachment 1).

Attachment 1





Or, after the combo box is set up, I can change the row source to point directly to the table and delete the query statement which seems more efficient (see Attachment 2). However, it also looks suspiciously like a lookup field.

Attachment 2


So, the question is: Which version is correct? Or, are they both correct and it doesn't really matter how the row source is populated?

[June7]

Yes, that is exactly what a combobox is for.

If you point directly to the table then all fields are retrieved. The SQL statement limits to just the necessary field(s).

[Missinglinq]

And no, that is not a Table-level Lookup Field, which should be avoided! Go here

www.mvps.org/access/lookupfields.htm

for an explanation of why Table-level Lookup Fields should be avoided.

Linq ;0)>

[ssanfu]

I can change the row source to point directly to the table and delete the query statement which seems more efficien

No it is not more efficient.

If you set the row source to a table, you cannot sort the data and cannot limit the records returned to a specific sub set.
If you have a table of names and addresses, using a table as the row source, you would see all of the names and states. If you wanted to just see the names in the state of Washington, a query (SQL) would be able to limit the records returned and have the names sorted.

My combo boxes always have a query (SQL) as the row source - except if the table only has a few records (under 5).

[Eddy Sincere]

Thanks for the answers! My question was answered and the issue resolved.

[Missinglinq]

Glad we could help!

Good luck with your project!

Linq ;0)>