>I'm working on an application that has many class libraries (VCXs) in the project. In the startup code, there is a SET CLASSLIB TO...ADDITIVE command for each and every VCX. The same goes for procedures; SET PROCEDURE TO ... ADDITIVE. Is there any drawback to doing it this way? I was wondering if there is any advantages of loading them on a "as needed" basis. Something along the lines of
>
>IF !"SOMECLASSLIB"$SET("Classlib")
> SET LIBRARY TO SOMECLASSLIB ADDITIVE
>ENDIF
>
>Then when its not needed, just RELEASE CLASSLIB SOMECLASSLIB. Would this be a more efficient use of RAM and/or does it affect the speed in any way?
>
>TIA,
>Mike

Hiya Mike!

I also have a lot of classes and procedures loaded at startup. They are primarily MaxFrame stuff. I use newobject for other classes as needed. I deliberately build functions/procedures as separate files. They get embedded in the exe - as they should be. They can be called without any need for SET PROCEDURE TO, as either functions or procedures. VFP seems to access things in the exe more quickly (directly?) than things inside a procedure inside an exe.