>>>George,
>>>
>>>>>>>My _screen.forms(1).name returned this also -- _parentclassbrowser
>>>
>>>>Unless someone says that it is a known issue before I leave at 5 PM ET, I'll report this tonight. Thanks again.
>>>
>>>_screen.forms(1).name = _parentclassbrowser
>>>_screen.forms(1).baseclass = toolbar
>>>_screen.forms(1).parentclass = Superclasstoolbar
>>>
>>>It's the Superclass thing that remains active after closing the Class Browser. See it on the main screen?
>>
>>You mean the toolbar? Yep that's it! For some reason it's not being released. Thanks for the info, Dave.
>
>In the Destroy of the BROWSER form, I put the following code at the end:
>
>_screen._oParentClassBrowser=.null.
>
>I too am using Ken Levy's superclass in addition to all this, but the browser also creates this 1-button toolbar that works like the one Ken did [probably is Ken's]. When you first start the browser, the APP adds the above object to the _screen. I guess the VFP Dev team saw no reason to remove that toolbar object when the browser was closed.
I've come to that conclusion as well. Since this is, at most a minor annoyance, and doesn't appear to hurt anything (or fix anything if released), I'm not going to bother to report it. If it gets to be a bother, I can fix it myself.
Thanks for your help, Mark.
>
>Since I do not care if that toolbar remains, I will probably be removed that code. It was mainly a test anyway. I don't think any of this has any bearing on the blue screen problems people have been experiencing.
George
Ubi caritas et amor, deus ibi est