>_Screen.AddObject("tool","_tool") >?_screen.tool.Run() >CLEAR ALL >?_screen.tool.Run() && where is my tool? > >define CLASS _tool AS custom > name="_tool" > > PROCEDURE Run() > wait wind "tool..." > ENDPROC >enddefine >Yes, this would be nice. I had the VFP developers look closely at this issue in VFP 3.0 when I created the Class Browser and also in the following versions of VFP when I was working on other FoxPro based components. This is simply a feature that has not and never will be added to VFP unfortunately. I think the two instances of VFP side by side (one to edit components and one to run apps) is worth a try if you are in a situation that benefits from it (avoiding CLEAR ALL).