Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Mike Dershowitz
  Where is Mike Dershowitz?
 Philadelphia
 Pennsylvania - United States
 Mike Dershowitz
 To: Eric den Doop
  Where is Eric den Doop?
 Houten
 Netherlands
 Eric den Doop
 Tags
Subject: RE: Form Handling - SOLVED!!!!!!!
Thread ID: 453 Message ID: 502 # Views: 4 # Ratings: 0
Version: Unknown Category: General VFP Topics
Date: Friday, June 01, 2001 1:12:27 PM         
   


> > > > Eric:
> > > >
> > > > Thanks, the clear events and thisform.release worked. But, what I really want to do is close the form? If I release it, the program continues just fine. The form still appears, but is not active. I can still click on it. Additionally, as you suspected, the x in the upper right of the form doesn't work. I can click on it once, at which point it goes transparent. Then, I can't use it at all.
> > > >
> > > > Thanks for your help thus far, and thanx in advance for your help.
> > > >
> > > > Mike
> > >
> > > Mike, if i understand you correctly, the form still exists even after the thisform.release? In that case, i think there is something wrong in the forms code, for example the queryunload (fires when clicking the X), or the unload or destroy or the release method itself. Have you got a NODEFAULT somewhere in your code? Are you using BEGIN TRANSACTION ... END TRANSACTIONs? Share some of the forms code with us so that we can help a little better.
> > > --
> > > Eric den Doop
> > > www.foxite.com - The Home Of The Visual FoxPro Experts
> >
> > Eric:
> >
> > Yes, the form still exists after the thisform.release, which is contained in a button procedure. Now, upon somone else's suggestion, I have a clear events and return statements in the destroy event. However, it is still not working.
> >
> > I am not using the transaction statements, and should I be? As far as a no default statement, I checked my code and it isn't anywhere. I am not using the unload method at all. just the destory and thisform.release, which I thought was the way that you close a form in foxpro.
> >
> > Thanks agian for all of your help.
> >
> > Mike
> >
>
> No you dont have to use TRANSACTIONs but i thought of that because you can't unload a datasession if a transaction is still active. Lets try a different approach:
> * comment (with the *) the code in the destroy and release events
> * in your close button (lets say that this button is called cmdClose), type
> thisform.release
> CLEAR EVENTS
> * in the queryunload type:
> thisform.cmdClose.click
> NODEFAULT
>
> Run your form and see what happens.
>
> --
> Eric den Doop
> www.foxite.com - The Home Of The Visual FoxPro Experts

Eric:

Got my form problems solved. I was setting a varaible equal to an object, instead of the value of those objects. I guess the sustaining of those objects was occuring on the release of the form, in the variables that I was setting them equal to. And this sustaining was preventing me from truly releasing the form.

Thanks again for all of your help. Now see me next problem posted today called "Nesting if's in a case statement." Hope you can help.

Thanks!!
Mike


ENTIRE THREAD

Form Handling Posted by Mike Dershowitz @ 5/30/2001 4:50:57 PM
RE: Form Handling Posted by Ryss Unger @ 5/31/2001 10:33:02 AM
RE: Form Handling Posted by Mike Dershowitz @ 5/31/2001 4:40:49 PM
RE: Form Handling Posted by Eric den Doop @ 5/31/2001 5:08:24 PM
RE: Form Handling Posted by Mike Dershowitz @ 6/1/2001 9:01:37 AM
RE: Form Handling Posted by Eric den Doop @ 6/1/2001 9:44:58 AM
RE: Form Handling Posted by Mike Dershowitz @ 6/1/2001 10:03:23 AM
RE: Form Handling Posted by Eric den Doop @ 6/1/2001 10:22:34 AM
RE: Form Handling Posted by Mike Dershowitz @ 6/1/2001 11:05:48 AM
RE: Form Handling Posted by Mike Dershowitz @ 6/1/2001 11:48:46 AM
RE: Form Handling - SOLVED!!!!!!! Posted by Mike Dershowitz @ 6/1/2001 1:12:27 PM