Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Weird thing about .Destroy
Message
From
08/11/1997 14:02:59
 
 
To
08/11/1997 10:51:37
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00058959
Message ID:
00059099
Views:
31
>>>>
>>>>You age going from some object on form, right? So, you first check Thisform.DE.Name or This.Parent.DE.Name. If its type is not "O", then you have thisformset and use This.Parent.Parent.DE or Thisform.Parent.DE
>>>
>>>And then you put the name in a form property? Like this:
>>>THIS.cFormName = THISFORMSET.Name or THISFORM.Name, whichever is appropriate? Then I suppose you use name substitution or macro substitution wherever you mention the DE, like (THIS.cFormName).DataEnvironment or whatever syntax works? I certainly don't want to check for the existence of a formset every time I mention the DE.
>>
>>I wouldn't use neither form property, nor macro substitution. I would just split my code. Again, it's question of personal preference. If you like your approach, and it works, then it's the best way to do.


>You could use the Name option of the DO FORM command but ofcouse
>this presupposes that you have the name of your form in your nav-buttons.
>


You could keep a global variable that keeps just the name of the
active form, then use that in your nav buttons class. I've have
had difficulties with this approach though. I think your better
off going with Edward Pikman's suggustion.

Dan
Previous
Reply
Map
View

Click here to load this message in the networking platform