That is what i thought was happening. Do you or anyone know where i might find some documentation, that would explain the memory usage of standard modules vs classes? I am new to this application, and i need to be able to show the director the benefits of going to classes.

I checked the MSDN. It explains the difference briefly, but i need a little more info.

Thanks

>As soon as soon as a sub or a function is called, the complete module in which it is sited is loaded in memory and stays there until the application quits. Classes are unloaded when you unload them manually (set x = nothing) or when they go out of scope. So it will use less memory to use classes.
>
>>I have an application written using roughly 8 standard modules, and no class modules. The standard modules all together include a total of around 4000 different sub routines. I was thinking of breaking some of the sub routines out of the standard modules and making them classes. Are there any advantages or disadvantages to doing this? Or is it event worth the effort of doing this?
>>
>>Specifically, will it cause the app to use less memory at runtime?
>>
>>Thanks in advance.