>_SCREEN?
>_VFP?
>
>These are what we use in testing to avoid the CLEAR ALL issue.
>
>>
>>The VFP team has looked at the CLEAR ALL issue carefully back to the VFP 3.0 days, and there has never been a good solution to implement based on the fact that those tools are VFP objects in the same memory space.
>>
>>Just give us one new system variable - _TOOLCOLLECTION - that can take an object reference, that doesn't get cleared with CLEAR ALL. We'll do the rest.

But that doesn't prevent a CLEAR ALL from closing the Toolbox, Class Browser, or any other Xbase component that is running. We've had the top VFP C++ developers review this issue for many versions of VFP to see what could be done, and we had a prototype of it working during the VFP 6.0 development days but it was cut and not included due to too many negative issues and problems that resulted in it.