Hi all,

I have a report that is giving me this error. It's been working for quite 
a while, so it's hard to explain why expression space is a problem. 
It _did_ have problems with expression space a while back. I 
moved as many variables to the calling command file as possible, 
and, as I remember it, I _just_ squeezed under the limit. I learned 
in that process that views share expression space, so I may have 
modified a view that had ill effects here.

So here's my question... it seems that I should be able to move my 
lookups to a stored procedure (though I've never used them in 
reports before). Would that help, or am I just shifting the problem 
from one place to another?

Thanks,

Ben Petersen

Reply via email to