Yeah, "10 times slower" sounds like something that one should be paying attention to, and there certainly must still be cases where that is still relevant, if called zillions of times. I've never been at the end of my rope, however, where attention to other broader issues in program design weren't more important to the issue of performance.


>>RE: Major Performance Penalty
>>
>>Is this type of thing still an issue? I mean, CPUs are so fast now ... not that performance isn't an issue (I have one calculation that runs for 20 minutes), but rather that it seems that the overall design seems to be of much more major of a concern that the internals of how VFP does things.
>
>Just looked at my notes on this (which happen to be in the Hacker's Guide, where everyone can read them <g>). At my last testing, having:
>
>

>*MyProg.PRG
>PROCEDURE MyProg
>* Code starts here
>

>
>was 10 times slower than:
>
>

>*MyProg.PRG
>* Code starts here
>

>
>in VFP 6 and earlier, but the penalty was gone in VFP 6 SP3 and VFP 7. Haven't tested since then.
>
>You also raise a good question about the importance of such things in an era of fast CPUs. It depends, of course, on how many times you make such calls.
>
>Tamar