Hello again Gene, I just re-read part of what you wrote below " The current method will have to finish first before the next event will fire " - and that DOES Seem to be what is happening. I didn't really HAVE a Release Method - or rather - I didn't have any Code in the Release Method for the Form. I did put in a Wait Window - and, sure enough - during the Inquire mode - the Wait Window popped up. And, even during this PO Create mode - where I am having the problems - the Wait Window ALSO Popped up. But, as you said - its trying to finish the REST of the code in the Method. My bad - I simply needed to put a RETURN after that called to Thisform.Release - and that should do it - and Stop it from running other code!
Thanks again for Steering this here Reynard in the Right Direction - like towards a Hot Vixen! :-) -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Gene Wirchenko Sent: Thursday, June 13, 2013 4:12 PM To: [email protected] Subject: Re: Silence & Problems Releasing... At 12:23 2013-06-13, "Kurt Wendt" <[email protected]> wrote: >.I hope nobody takes the humor in that Subject the wrong way. I note that yours was the only post to ProFox today so far. Is that the wrong way you were thinking of? Oh! No, now, I think I understand. I am sorry. I took the subject in the wrong wrong way. >Sure has been Silent on the List here lately! Seen NO Messages since Early >yesterday. Must be just because VFP is So Rock Solid that nobody has >problems anymore. You may think that you are being facetious, but there is a real side to that. Programs that just work do not require support groups. >OK - onto the issue at hand. This is allowed. >I have this screen I have been working on (which, of course, was initially >produced by my Screen Hacking Utility). Initially - the screen was only used >to Inquire PO data. Then it was updated to allow one to Modify PO data. Now >- the final updates will allow a user to Create New PO's with this screen. >Its during this PO Creation Processing that I am now having a strange >problem. > >In another area of the program - I use the following command to shut the >screen down: > > Thisform.Release > >And - strangely enough - it doesn't seem to work at all today - in the new >part of the screen! I used the exact same command for the Inquire Mode - and All I can think of is multiple references to the object. >it Does shut down the screen. But, now when I used it in another area - it >seems NOT to Work! I even STEPped thru the program - and I saw it supposed >run that Line of code - then continue on with other code after it - as >though it did NOT do ANYTHING or even Run that line of Code!!! The current method will have to finish first before the next event will fire. I suggest that you put a set step on in the release method to see if it is firing. I have found that stepping through code that has screen effects sometimes results in different behaviour with Refresh being particularly nasty for this. >What Gives? Anybody seen this before? Am I losing my Marbles??? Time to find >a new Career Path? > >:-) Answer to #3. It is possible. Just in case, here is a link for you: http://www.rainbowturtle.com/SearchResults.asp?Search=marbles Sincerely, Gene Wirchenko _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/8E03539444524CBA97D9F7DE8C5280A2@Programming2 ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
