Hi,
We are challenging problem with high consumption of windows user objects by datawindow. Windows are limiting processes to 10.000 user objects, it is quite simple to reach this limit in big MDI applications which are using many datawindows. Once application hit 10.000 user objects (that is approximately 100 mid size open datawindows), than it become uncontrollable and start causing windows instability. Windows will stop rendering application and also whole desktop will start having problems with rendering. We addressed this issue by monitoring consumed user objects and restrict user to open more windows in application. This is quite limiting, I can see that other applications showing similar amount of data are consuming significantly less user objects. Wouldn't be possible to optimize datawindow rendering to consume less user objects to prevent such situation?
Regards,
Marian.
Thanks for tweak, but we are not using much datastores in our app. It did not help in our case. We have classic MDI app with many complex multitab windows, where each tab have datawindow. Users can open only around 8 of this windows simultaneously before they hit user object limit. If they are opening simple windows with 1 to 4 datawindows, than it is no problem to open 100 of them. My wonder is if datawindow rendering method do not have somewhere forgotten release of user objects after rendering is done.
Regards, Marian