Elmer,

>>This thread reminds me of the M. and not to M. thread arguing the merits of using M. or not when referencing memvars. This too appears to be a matter of programming style and whatever works for you.

On the issue of m.... Fox searches for a fieldname matching before it looks for . If you always preface with m. you get a slight performance boost, so there is an objective reason for following this practice.

Conversely, IIF() has slightly better performance than IF/ENDIF... at least that's what I was told back in the dBase III days. These days, who knows?

Regards,
Thom C.