>Good point Liam, I forgot about the SET CLASSLIB string!
>
>As for your 2nd point, I used to favour keeping all functions & procedures in their own .prgs, as it was easier to work with these in a team development effort in 2.6 days. Also, it didn't mean a huge big file was compiled when a small change was made to just 1 piece of code.
>
>Actually, I've recently begun to move all functions & procedures into classes, seems to be more in the "spirit" of VP 6.0.
>
>Thanks again,
>
> Andy Crawshaw

Hi Andy,

IMHO, there is nothing wrong in having procedure file or even certain procedures in separate PRGs (even in VFP 6 :) In many cases it is more "economical" if compared with the need to instantiate the whole procedure object for testing something. The access to PRG also appears to be faster.