Cindy;

I gave up using the m prefix with VFP 3.0, along with other things like scatter and gather. This I did for my own reasons. I am glad we all have our own approach to this subject. Sometimes we do something and establish a course or path. Occasionally we forget the details but it feels good to do things the same way. The fun begins when someone else has to read our code! Or dares to make us think of a different method. :)

Tom


>In a loop with a jillion iterations for a real-time application, speed might be important. For me, readability and ease of maintenance are important. Also, I'd rather use m. all the time than try to remember which coding situation I'm in.
>
>But those are my coding goals, not yours, and we all need to code in accordance with our goals. < G >
>
>>If Craig is correct, your rule has meant that your code has been up to 1/3 as fast as it should be. I think we should aim for the best balance of readability (which is minimally affected by globally having the m.), performance and stability.