Hi Jim,

What do you mean by "indirect reference"?

THanks

>Hi Spencer,
>
>Not so sure that that is true... here's an excerpt from "Hacker's Guide to Visual FoxPro 6.0":
>
>"What about performance? We often see people going to great lengths to eliminate macros from their code. But the truth is that, in certain cases, macros are actually faster than EVAL(). Here are some guidelines:
>
>Always use indirect reference rather than EVAL() or a macro. If FoxPro expects a name, indirect reference is the right choice.
>
>In a command that will be executed repeatedly, it's generally better to use a macro than EVAL(). The macro is expanded once and substituted into the command while an EVAL() expression is evaluated each time the command executes.".
>
>Cheers,
>
>JimN
>
>
>>Hi,
>>
>>Evaluate() is significantly more effecient than the & macro. As you get comfortable with evaluate() you'll want to consider using in place of a & macro whenever possible.