Combo filter bad message. Trying to use 2 combo fields on a form.

[gpierce9]

2/24/2018 Hello. I am having trouble with the 2nd combo box.


I get an criteria type of error.

The 1st combo is where I enter or pull down a STATE.
The 2nd combo is then supposed to show me the Airports applicable to that State.

For example, if I enter FL for florida in combo 1 and then I go over to combo 2 pull down,
UP pops the error message. For the heck of it, I entered FL into the error message.

I got what I wanted. I get to pick the desired airport.

So this combo dependent deal is almost working. I am doing something wrong.
I have this design for other places and it works. But not here.

You will notice in the 2nd combo box, inside the After Update, I have a criteria in the state field.
It is identical to the error message. So maybe I have something wrong in that criteria row ??

I looked around the forum and internet but just can't find an answer.
Small zipped file is attached. The frmCustomer holds the 2 combo boxes noted in Yellow.
Thanks. Glen.

[davegri]

Change rowsoruce for cboMailRegionDataID to:

SELECT tblMailRegion.MailRegionID, tblMailRegion.MailRegionName, tblMailRegion.AirportID, tblMailRegion.State FROM tblMailRegion WHERE tblMailRegion.State=[cboMailRegionState];

[gpierce9]

Change rowsoruce for cboMailRegionDataID to:

SELECT tblMailRegion.MailRegionID, tblMailRegion.MailRegionName, tblMailRegion.AirportID, tblMailRegion.State FROM tblMailRegion WHERE tblMailRegion.State=[cboMailRegionState];

I have attached a zipped file again for posterity!
In case anyone else needs this. Dave did a nice job for me.

2comboTest3.zip

Glen

[davegri]

Glad to help.
When you use expression builder for creating criteria, expression builder doesn't know where the code it is generating will be used. So, it creates full object names for for controls on forms.
If you know the code is to be executed on the form, you can strip off that [Forms]![frmName]! prefix stuff.

BTW, I like your GUI design for the form. Looks nice.

[ssanfu]

A couple of comments.....

EVERY module should have

Option Compare Database
Option Explicit

as the top 2 lines.



Instead of syntax like

   Me![cboMailRegionDataID].Value = Null
   Me![cboMailRegionDataID].Requery

you should use

   Me.cboMailRegionDataID = Null
   Me.cboMailRegionDataID.Requery

The brackets are only required if the name is a reserved word, has spaces or has special characters/punctuation.
"Value" is the default property, so while it doesn't hurt, it is not necessary (and saves you typing time)

Also note that "STATE" is a reserved word in Access and shouldn't be used as an object name.
See http://allenbrowne.com/AppIssueBadWord.html