Invalid Syntax or Operand without an Operator in a Query

[ArnieT]

In general, AfterUpdate event of first control (NB! You have to differ between fields, which are table things, and controls, which are elements of form. Controls have a table field as source, or they have an expression instead.) rewrites the Row Source of another combo box/list box. And of course, an OnCurrent event of form rewrites also the Row source of second combo box whenever another record is activated. There were sevaral postings about this in last couple of months - look for cascading controls/combo boxes/whatever.

Thanks a whole lot. Even though I am not totally in the clear, but I am starting getting the idea (I think) and will see what I can do with this. I hope the other postings will help to.



On the reflection, it does seem to make more sense not to use lookups in tables. I was not quite sure whether or not cascading tables were bad, but I didn't really like the look of them.

[ssanfu]

@ArnieT
What you are asking about is "Cascading combo boxes".


My bad. I should have posted the link about:
"The Evils of Lookup Fields in Tables". (This is different than Look up TABLES)
http://access.mvps.org/access/lookupfields.htm

also check out:
http://access.mvps.org/access/tencommandments.htm

[ArnieT]

@ArnieT
What you are asking about is "Cascading combo boxes".


My bad. I should have posted the link about:
"The Evils of Lookup Fields in Tables". (This is different than Look up TABLES)
http://access.mvps.org/access/lookupfields.htm

also check out:
http://access.mvps.org/access/tencommandments.htm

Thanks a lot. Will surely look into it. Appreciate all your help.

[ArnieT]

@ArnieT
What you are asking about is "Cascading combo boxes".


My bad. I should have posted the link about:
"The Evils of Lookup Fields in Tables". (This is different than Look up TABLES)
http://access.mvps.org/access/lookupfields.htm

also check out:
http://access.mvps.org/access/tencommandments.htm

I sure like the Ten Commandments. Makes sense. But will need to look into the Evils of Lookup Fields more deeply.