Hi Matt,

You SET CLASSLIB/SET PROCEDURE to create/control your invocation stack. Trust me, this is a good thing. Without this, VFP would need to load all the programs/VCXes in memory regardless of need, and finding things might not sequence the way you'd like.

I never include a OS path in my SET CLASSLIB / SET PROCEDURE statements. That's what SET PATH is for.

For more info on the VFP invocation stack, see http://fox.wikis.com/wc.dll?Wiki~VisualFoxProInvocationStack and, for more along these lines, http://fox.wikis.com/wc.dll?Wiki~VisualFoxproEnvironment

**--** Steve

>If I have added my class lib's to my project file, why do I still have to put code like:
>
>set classlib to f:\blah\library1
>set classlib to c:\vfp7\ffc\_table additive
>etc.
>
>It seems stupidly redundant. I told the computer which class lib's were assosciated with my app, and where to find them when I added them to the project, and I still have come back and programmatically activcate them.