>The thing that is interesting about this situation is this. You have a framework in effect that has a contract that states that the oApp will launch forms, then when FormA violates this contract you get a situation where oApp can't do its job correctly because there is something going on that it doesn't know about. The answer to the situation is to look closley at your framework and identify the contracts that exist. Then insure that those contracts are always enforced and that they are not bypassed for convenience sake.

I haven't had a use to use a oApp.aForm array to handle various information about forms. I think this is a good time to start it.

Thanks for bringing the word contract. When I followed your session on this, I remember you mentioned that at several occasions. This is definitely the right term to use and help the understanding.

So, by having this array, where a column of it might be to know if the form is parent or child, will allow me to close the parent form first. Am I on the right track?