query error with combo box

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Brian L - 03 Aug 2006 19:53 GMT

I'm doing a cross-tab query and using one Where clause that looks up a value
in a combo box. No matter how I build the criteria, I always get message:

"MS JET DB does not recognize '[Forms]![frm1]![cboName] as a valid field.

Oddly enough, it works fine on my other form. Any ideas?

Reply to this Message

Jerry Whittle - 03 Aug 2006 20:29 GMT

Crosstabs can be a problem especially with parameters which it might think
that your form is.

Try creating a normal query just to pull the appropriate records. Next build
your crosstab query based on the first query.

Signature

Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

> I'm doing a cross-tab query and using one Where clause that looks up a value
> in a combo box. No matter how I build the criteria, I always get message:
>
> "MS JET DB does not recognize '[Forms]![frm1]![cboName] as a valid field.
>
> Oddly enough, it works fine on my other form. Any ideas?

Reply to this Message

Brian L - 03 Aug 2006 20:35 GMT

Thanks. That partially worked. When I format the date to Monthly, it works
fine with the combo box criteria. But if formatted quareterly, it doesn't
like it one bit. Errors out right away. Perhaps I need to hard code the
output in SQL view? Who knows...

> Crosstabs can be a problem especially with parameters which it might think
> that your form is.
[quoted text clipped - 8 lines]
> >
> > Oddly enough, it works fine on my other form. Any ideas?

Reply to this Message

Duane Hookom - 03 Aug 2006 22:26 GMT

You must specify the data types of your parameters in crosstabs (unless you
include the column headings property) Select Query->Parameters and enter
Forms!frm1!cboName Text

Signature

Duane Hookom
MS Access MVP

> Thanks. That partially worked. When I format the date to Monthly, it works
> fine with the combo box criteria. But if formatted quareterly, it doesn't
[quoted text clipped - 18 lines]
>> >
>> > Oddly enough, it works fine on my other form. Any ideas?

Reply to this Message