Just got an email from our local experts circle and they claim that....a cls file once activated in a vb project remains in memory for the duration of that project.....

May be this could be the answer to a number of posts regarding memory usage? Don't know, our memory problems are generally to do with the number of dlls attached to a project.

Am so confused on this issue