>It still sounds like to me a case of mixed meatphors -- part FPW procedural coding and part VFP OOPS. VFP supports the procedural syntax of the FPW functions ( i.e. Wexist() ), but that does not mean that an object name has been made available to you. Try adding the 'NAME' clause to the 'DO FORM'. I suggest a "Hungarian" notation, beginning the name with 'go' for global object -- of course to be 'global' you need to code something like: "PUBLIC goName", thus, you wil have something like:
>
>Public goName
>do form xxx name goName linked
>goName.Activate()
>
>When you have completed using the form, you may simply: RELEASE goName to get rid of it.

Robin, this idea will not work when you start modeless form from menu procedure because variable is gone when procedure gets finished. The only safe way is to check _SCREEN.Forms() collection or build oApp collection to your own.