Thanks, Jim. This is what I told my colleague, who is currently in charge of Update application, but she told me, that otherwise the process would be much slower, since oPost would be needed to instantiate each time again (it has exessive Init and Destroy methods).

Anyway, I'll see her on Monday and will use your arguments in addition to mine.

Thanks a lot.

>>That's why this object is declared as public. I understand, what it really breaks a good OOP design, but both applications are not mine, and we don't want to make the process slower, than it is right now. That's why Validate should clean after Update. Not a good design, I agree, but I don't see a better solution in this situation...
>
>Nadya,
>
>I totally disagree with you here, no app should needd to clean up after some process it calls. That is not only bad OO design it is bad Structured programming design. It is plainly bad design period and if it doesn't get fixed now it will cause more and more problems as time goes on. It will cause spaghetti code to be produced repeatedly everywhere the app that doesn't clean up after itself is called.