>>>Hi guys,
>>>Also it can be that you have a field with the same name of the
>>>variable in the current work area, just a guess.
>>>HTH
>>
>>
>>Thanks for all your input. You won't BELIEVE the solution to the problem. I had two memory variables in the report which had 11 character names. When I changed them to 10 characters (or less), everything seemed to come out fine! I THOUGHT the extra characters were simply ignored, but appears that they can cause a nasty resource leak when used in a report.
>>
>>Thanks again.
>>
>>Valerie
>
>I've run into the same problem. Another nasty that I've had is alias names longer than 10 characters in a SQL SELECT statement in FPW 2.6.
>
>Craig

Craig,

Yeah, I've run up against that one too. Also, in FPW2.6 if your SQL SELECT statement runs too many UDF's or IIF()'s it will also cause a major resource leak! MORAL: KISS, Keep It Simple Stupid!

Valerie