We develop applications that go against multiple back ends, sometimes in a single form. I created a connection class that that has a collection of connections. For ease of use in the development environment, I instantiate a developer toolbar that has a combo box that allows selection of the desired connection handle so that builders have the proper connection after the initial login.

So far, so good. The problem comes when we CLEAR ALL, which happens about a zillion times a day. The tool bar and the connection-collection object evaporates, causing us to re-login over and over. In a single back-end environment, I would just put the connection handle on a _screen level property and it was immune to CLEARing. When I put the toolbar or collection object reference in a _screen level property, the object reference evaporates leaving the property NULL.

What would be nice would be a way to "protect" the _screen property. I suppose I could have a clean up proc issue a RELEASE ALL EXCEPT... instead of the CLEAR ALL, but I'd sure like to keep the ability to CLEAR ALL. All suggestions welcomed.

Gary