>>Are you compiling the app as a single monolithic .EXE or multiple .EXE's?
>
>Multiple exe's.
The loading and unloading of class libraries into memory definitely behaves differently in that situation. You shouldn't have the problem with a single .EXE (which may or may not be an option for you).
This is a SWAG but since VFP is by nature single-threaded it appears that each EXE loads the class lib into a separate chunk of memory. Once in, it doesn't come out, or at least can't be cleared by a different EXE (I don't know if the EXE that loaded it can successfully remove it). We had a similar situation in an early version of a project that was compiled into multiple APPs called by a central EXE. Moving to a monolithic EXE solved that problem and several more.
Hope that helps...
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
