Mike,

I'm not sure that's entirely correct because of the way in which FoxPro searches the calling stack. As I recall, & correct me if I'm wrong here, the current file is searched for the procedure or function & then any procedure file. This is then followed by a trace through the entire calling stack, finally looking for a file with the correct name in the path.

So, putting your routines in a procedure file, although an 'old' technique, may well improve your application execution speed despite today's fast computers especially if you are calling several routines in the middle of a scan or other loop that loops many times.


>>Wouldn't it be very messy if I got dozens of procedures? Then I would I lots of files inside the project manager.
>>
>>Can we put it all inside a lib of something like the Pascal or C langage do?
>
>Just because another language can do something, doesn't mean that it was a proper thing to do then or for VFP now. The old technique of putting all functions and procedures in one file is just that, an old technique. Excepting the operating systems ability to handle long file names, there is nothing lost by having a large procedure file broken into separate prgs.
>
>Mike