I use calculated fields in queries all the time. I have noticed an annoying flaw with them I'm hoping someone can help me get around it.

I often use a calculated field nested in a second calculated field and it works just great. However, if I add criteria to the second calculated field, or I try to sort the second calculated field, Access then decides that the first calculated field nested in it is really a parameter. That is, it prompts me to type a value and the "question" it asks is the name of the first calculated field.

Why does Access process nested calculated fields properly when no criteria or sort order are set on the second one, but then thinks the first one is a parameter to prompt for when the second one gets criteria or a sort order? :(

I'm using Access XP (2002). Thanks in advance.


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

__________________
Greg Serrano
Michigan Dept. of Environmental Quality
Air Quality Division