Basing combo box on field in TABLE in Access 2007

[TimothyBendt]

I understand the code

SELECT Brand.[Brand Name], Company.[Company Name]
FROM Company INNER JOIN Brand ON Company.[Company Name] = Brand.[Company Name]
WHERE (((Company.[Company Name])=[forms]![project]![company name]))
ORDER BY Brand.[Brand Name];

As it will only show the brand names from a particular company previously selected in the form. However, this code works in a form but not in a table. What is the equivalent code for a table?

Thank you very much for your help

[TheSmileyCoder]

Tables are for storing information, and forms are for presenting and modifying information.

That said, its possible to do something similar, its called a Lookup field(google it). However I strongly recommend against them, and so do other Access developers, see The Evils of Lookup Fields in Tables

[TimothyBendt]

I've been looking around a bit and still having some trouble. Do you know if it's possible to use a lookup field to get data from a different field in the same table in table form (as opposed to getting data from a field in a DIFFERENT table)? Regardless of the consequences.

Thank you for replying!

[TheSmileyCoder]

I am unsure what you mean by table form? Is that a table or a form?

If you are using a form, I suggest you take a look at:
http://bytes.com/topic/access/insigh...mbo-list-boxes

[NeoPa]

I believe that should be possible. If you have tried and failed then let us know, in detail, what you've tried and what resulted, and we'll do what we can to help you regardless of our own opinion on the advisability of the approach.

NB. ** Warning **
I'm sure you already appreciate that this is very much something most people warn against, or at least if you don't, then you have elected not to follow the warnings given anyway, but others may not appreciate the position. It is for them that I add this warning that using ComboBox features within a table design can lead to all sorts of troubles and issues. I've taken on projects before where these have been used, and working on them is so frustrating as they often break after changes are made to the related tables, and working with them becomes a real slog.

[TheSmileyCoder]

Weeks of work can quickly save you hours of planning

I have always loved that quote.