G
Guest
Hello: when running a select query containing a field dependent on a
calculated field (which is also "housed" in the same query), I am getting a
parameter popup. I have double-checked the spelling and even changed the
field name & copy/pasted in all appropriate places. I know from seeing this
before that if I can put the calculated field in one of the source queries,
this parameter error will go away. Only thing is, not able to do this now
due to the joins I need--would rather not create another layer just to handle
this single calculation. Is there a patch or something else that will
address this? Per Help, it should work so long as the calc'd field is made
visible, which it is. Why does this occur?
calculated field (which is also "housed" in the same query), I am getting a
parameter popup. I have double-checked the spelling and even changed the
field name & copy/pasted in all appropriate places. I know from seeing this
before that if I can put the calculated field in one of the source queries,
this parameter error will go away. Only thing is, not able to do this now
due to the joins I need--would rather not create another layer just to handle
this single calculation. Is there a patch or something else that will
address this? Per Help, it should work so long as the calc'd field is made
visible, which it is. Why does this occur?