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.

(I started work 30+ years ago, in a now-dead language, APL, where we all knew how all of the internals worked, as we were always worried about performance. As time went by however, these diminished in importance when compared to the structure of the application and the algorithms chosen.)

>>[1] It appears that this works only when you have a project open. As I haven't usually worked that way, it seems like this capability alone makes it worthwhile always to have the current project open.
>
>Actually, I think it also works in a folder hierarchy.
>
>>[3] "View Definition" only finds PROCs that are defined with a PROCEDURE or FUNCTION statement. Thus, a PRG named 'MyProgram.PRG' which does not begin with a PROCEDURE statement will not be found. (I usually only add PROC of FUNC to the first line of PRGs if there are more than one in the PRG.)
>
>Good point and one I hadn't thought of. I haven't tested this for a long time, but there used to be a major performance penalty for a PRG that started with PROC or FUNC.
>
>Tamar