Naomi,

It's too late, I read it :-)

I have mostly eliminated macros from my code. I agree they're harder to trace and debug since they involve direct substitution. Sometimes they are easier to use up front but payment comes later.

Thanks,

Irv.

>>To All:
>>
>>Regarding &,Evaluate() and (name expression):
>>
>>What are the functional differences and limitations of these three commands within Fox? The Help says to use (name exp) and Evaluate() rather than '&' whenever possible. I see them all used succesfully within code and was curious on everybody's input.
>>
>
>Just my 2 cents before you read the other thread. If name expression or evaluate can be used and it's not in SCAN &lcCond similar construct avoid macros by any means. They made code so harder to read! My former colleague for some unknown reason was a favorite of macros and I had to dig through the whole code and do replacements to make this code readable.