Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
This one has me baffled
Message
From
30/03/1998 00:33:45
 
 
To
29/03/1998 23:52:15
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00088012
Message ID:
00088018
Views:
23
What you do is not really correct. First, you assume that the file name of the form is the same as the form's title. This maybe be true sometimes, but, usually, it's not.

The right way (or one the right ways :)) to do this is to scan the Forms collection of the _VFP object and see if the form exists or not.

Vlad

>A menu option calls the procedure with a parameter (the form to launch mFormName):
>
>PROCEDURE LAUNCHFORM
>1 if wexist(mFormName)
>2 mCommand=mFormName+".Show"
>3 &mCommand
>4 else
>5 do form &mFormName
>6 endif
>RETURN
>
>which, to my simple mind should work.
>
>Lets say the form has not been launched and so does not exist in this instance of the app. Calling the code above correctly launches the else portion and launches the form.
>
>If I immediately call the procedure again, via a second call to the menu option, the code pukes at line 2 with the error "Object OUTGOING is not found". (OUTGOING being the value of mFormName). It has correctly identified that the window does exist - and it does because I can see it on the screen - but it ceases to exist in the sense that I can call its "Show" method.
>
>A LIST OBJECTS at this point confirms that the object does not exist ... or does it ? Or is a window not an object ?
>
>Gerry.
Previous
Reply
Map
View

Click here to load this message in the networking platform