David,

>> So if you expect the number of concurrently active objects to grow beyond a few thousand and/or not too current hardware is used, you might recommend this easy "optimization" <g>.
>
>Actually I think I'd recommend a redesign of a system that had a need for that active objects. *g*

*That* was the easy part! Since I was brought in fairly late I was not to blame for the design of the home grown framework. The difficult part was to decide on how to speed up *within* the framework, its interfaces and the "code grown over" it, since a couple of million EUR in programmers' wages were already spent building on top of the framework <g>. And since it was first try at OO for most of the programmers there, there were other problems as well. But to be honest, the apps HAD to be quite object heavy (insurance sector) since the number of visible controls in some branches could exceed 500, spanning quite a few tables. Yes, there were options to separate into different screens, but it was too late to go in and rip out heavily without giving already deployed apps a hard time.

regards

thomas