Cascading Combo Boxes in a TABLE (not a form)

[timandlindsay]

I am trying to populate a "Contacts" field combo box based on the information given in a "Company" field in a TABLE. I have found a number of people solving this issue using a FORM, but I am specifically look to do it in a TABLE.

I have read a number of sites that recommend NOT doing so in a TABLE - but no explanation of why not. I use the table to input new data and modify old data - and maybe I shouldn't be, but that's all I know of Access so far (I'm a newbie).

[isladogs]

Using combos in a form is absolutely fine - both individual combos & cascading combos

Table level lookup fields (AKA combos at table level) are definitely NOT recommended
Here are two links that explain the main reasons for not using them:
The Access Web - The Evils of Lookup Fields in Tables (mvps.org)
Table Lookup Fields - Mendip Data Systems

I don't understand how it would even be possible to have cascading combos in a table.

[Bob Fitz]

There is no good reason to use lookups in tables, after all, tables are for storing data, queries are mainly for retrieving data, forms are for entering/editing data and reports are for displaying data.
The following link is one that is often offered as help with why Lookups should NOT be used in tables but rather in forms.

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