Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Unknown (x) datasession wreaking havoc.
Message
From
21/11/1998 01:29:05
 
 
To
20/11/1998 18:27:18
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00160029
Message ID:
00160097
Views:
17
David,

I just posted a similar problem (Thread 160084) late today (GMT)

If you have instantiated an objcet from within the form (F2PiclList), and if that object is not released prior to the form's release, then the PrivateDS fails to close automatically. This is a behavior I observed a couple of months back, but just needed confirmation.

The reference to the object (see my thread) is a PUBLIC var. However, if it was PRIVATE or LOCAL, the PrivateDS closes OK.




>I have a modeless form (frm1), private datasession calling a modal form (frm2), private datasession. This form, in turn, can call a modal form (F2 picklist) needed. The when frm2 returns to frm1, without call F2 picklist, everything is fine, however, if the the F2 picklist (or any modal form) is opened from frm2, then problems start happening. the datasession for frm2 does not go away, and frm2 is still resident in memory as a null object. Even after releasing this null form, the datasession for frm2 does not go away. Normally, this would not be a problem, however, I need to do a refresh, to update frm1 based on the return from frm2. During the refresh, the datasession jumps to the unknown(3) datasession from frm2. I am able to catch this in the first refresh method that it comes across, but I doubt that trying to catch it there is prudent.
>
>If anyone has had a similar problem or knows how to fix this, please let me know. I think that if I could just remove the unknown(3) datasession from memory, then my forms would be happy.
Kenneth.
Previous
Reply
Map
View

Click here to load this message in the networking platform