Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
A little problem
Message
 
 
To
23/01/2004 06:48:48
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00869802
Message ID:
00869948
Views:
13
Fabio,

You seem to find truly obscure things to try to force VFP into doing.

Why would you really need to use a DEFINE WINDOW form in the first place? You are mixing old 2.x styles of code into O-O based code.

You should create a "real" form as part of a goApp object and then your forms can make requests of goApp to display your messages. goApp can keep a reference to the form or iterate the _screen.Forms[] collection to find it.

>On DEFINE WINDOW Command help session:
>
>NAME ObjectName
>Creates an object reference for the window, allowing you to manipulate the window with object-oriented properties available for the form object.
>

>
>Then, without NAME the window it is or it is not a object ?
>
>The answer: It is a object, always
>
>This have a impact on the private datasessions
>- i cannot DEFINE a free text window ( audit, messages, ... )
>directly on the fist private datasession opened, and share this with other private datasession.
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform