>Macros have no effect on Rushmore. If the criteria is optimizable rushmore will optimize it. It has always been this way.

Well, I'll be @%*! I hate it when something I "knew" for years turns out to be dead wrong. I'd swear I'd read somewhere long ago that Rushmore was (at least partly) turned off by using a macro substitution in your FOR expression. Maybe what I'm thinking of is the warning that macro substitution in a SCAN FOR loop won't change your ending condition as the value in the macroed variable changes, since the macro is only expanded on the first iteration of the loop. I know there was SOME reason you weren't supposed to use macro-substitution in FOR clauses...

>As for eval() or name expressions versus macros, they are simply faster at expanding the expression than a macro is.

This I knew.

Thanks for the eye-opener,
Rich.