Unique values for combobox

[neuk]

I have a table named "Categories". I have a field named "Method" in that table. I would like to display unique values from the said field in a combobox. To test this out, I created a blank form, added the combobox, went into the Query Builder form, set "Unique Values" from the Query properties to Yes. I then ran the query and everything displays just the way I want it. I then save changes to the combobox but when I go to Form view the combobox is empty.



I checked the row source and true to form it says SELECT DISTINCT Categories.Method FROM Categories...so why then does this only work when I run the query but not for the combobox?

I must have been playing around with this for hours to no avail. I find that when I follow this process on an existing query instead of a table it works just fine with the combobox - it just doesn't seem to work with a table. Any ideas what I could be doing wrong?

[neuk]

It seems to have something to do with the subdata sheets. After getting rid of them I notice that it works...not sure why. Talk about trial and error.

[orange]

I then save changes to the combobox but when I go to Form view the combobox is empty.

Data is stored in tables. I'm not sure what you expect or mean by saving changes to combobox.
If you set the row source property of the combo to SELECT DISTINCT Categories.Method FROM Categories and saved the form design, I would expect the form and combobox to be consistent.
Perhaps there is more to your set up.

[ArviLaanemets]

It seems to have something to do with the subdata sheets

Is OP creating forms as datasheets?

[neuk]

The asnwer to my question appears to be here, item 2:

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

[neuk]

Data is stored in tables. I'm not sure what you expect or mean by saving changes to combobox.
If you set the row source property of the combo to SELECT DISTINCT Categories.Method FROM Categories and saved the form design, I would expect the form and combobox to be consistent.
Perhaps there is more to your set up.

You SELECT the fields, FROM the table generated by the object (WHERE) known as the combobox. That SQL is part of the script saved under the combobox which runs every time you select the combobox (that's how the combobox generates the queries from the table). So when I say "save changes to the combobox" I'm talking about the script, not the data...

[orange]

Most developers/responders will advise you to ignore/avoid lookup fields in tables.
It still isn't clear to me what you are trying to accomplish. Perhaps you could describe your intentions in plain English.
Since you seem new to database and Access, I recommend that you review some of the articles at the link to Database Planning and Design in my signature.
You appear to be working with Forms and Controls which are associated with user interface typically. I suggest you focus on describing the "business" that you wish to automate with this proposed database, and work through 1 or 2 of the tutorials from RogersAccessLibrary mentioned in the link above.

Good luck with your project.