Class module size \ Memory usage
What are the implications for a large class module and memory usage?
We've recently inherited a project that has a huge class module that is basically a data access layer, has lots of methods for retrieving & updating data etc - it exposes hundreds of methods. (I can sort of see what the programmer was thinking, but he could've encapsulated into smaller classes!)
I remember having a problem with large standard modules, since all the code contained is loaded into memory when you call a procedure within the module - client machines were running out of available memory! Does anyone know if it is the same thing for classes when you instansiate a new object, or does it just locate & allocate memory when you call methods?
eg;
Code:
Set x = new MyObject
'All the code contained is now loaded into memory???
Any thoughts?
Cheers
Re: Class module size \ Memory useage
As far as I'm aware, it's the same for all kinds of modules. I agree it should probably be split up.
Re: Class module size \ Memory useage
hmmmm - kind of what i was thinking but not a task I particularly want to do...! painful code changes...will put it off for as long as possible....!
thanks tho