>Jay,
>
>In the context of optimizing code: We are not "big," but rather "busy."
>
>But not too busy to use SET TALK or to optimize your code according to the optimizing tips in the online VFP help... right?
>
>Which is why it is reasonable to see these same behaviors included in any performance example. We all do it- how many gurus over the years have shown us how to include it in our base classes- so "trick shots" that remove such a "normal" component to prove a point, are not as relevant as some would have it.

John,

Ok, I'm with you on the use of basic performance code mechanisms, but I'm not sure that's what Terry and I were discussing. I was under the impression that he was discussing fine-tuning optimization to a much higher degree. I was just saying that often there isn't time for that due to other priorities.

Are we somewhere near the same page?