By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,734 Members | 1,358 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,734 IT Pros & Developers. It's quick & easy.

Expression too complex to be evaluated

P: n/a
I'm receiving this message when running a query...

This expression is typed incorrectly or is too complex to be
evaluated. For example, a numeric expression may contain too many
complicated elements. Try simplifying the expression by assigning
parts of the expression to variables.

Here's the background. I have a query. I've figured out through
cutting and pasting which field is the culprit. So I have a field with
the following info...

eecat: Cat([allemp_12312007]![employment_category])

The function cat esstentially converts the values in the employment
category field to a numeric using a case statement.

Then I have this as my criteria for the field...
>[forms]![frmSwitchboard]![frame42]
Frame 42 is an option group with two options.

If I remove the criteria line, it seems to work fine. The baffling
part for me is that I have the exact same setup in another query (just
based on a different, but almost identical table) and it's working
fine. Any ideas?

Thanks.
Jun 27 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On May 12, 2:43*pm, Coll <col_mcma...@hotmail.comwrote:
I'm receiving this message when running a query...

This expression is typed incorrectly or is too complex to be
evaluated. For example, a numeric expression may contain too many
complicated elements. Try simplifying the expression by assigning
parts of the expression to variables.

Here's the background. I have a query. I've figured out through
cutting and pasting which field is the culprit. So I have a field with
the following info...

eecat: Cat([allemp_12312007]![employment_category])

The function cat esstentially converts the values in the employment
category field to a numeric using a case statement.

Then I have this as my criteria for the field...
[forms]![frmSwitchboard]![frame42]

Frame 42 is an option group with two options.

If I remove the criteria line, it seems to work fine. The baffling
part for me is that I have the exact same setup in another query (just
based on a different, but almost identical table) and it's working
fine. Any ideas?

Thanks.
I think I may have figured it out, so no need to respond. Thanks.
Jun 27 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.