Rafael, All the events are firing at the right time in the correct sequence and I've just managed to create exactly the same problem with the scope operator. However this occurs less frequently than with the DoDefault() method.
My feeling is that this is a timing issue as Allen suggested. As a matter of interest I have also just loaded up VFP7 to run the same code and I just can't get it to go wrong no matter what I do. I can't test it out with VFP8 as I haven't got a copy so maybe there is an issue with VFP9. On a positive front, what I have been doing is setting up a list of base classes for handling Client/Server which I intend to release for the benefit of others as soon as all the major bugs are ironed out (nearly there) and maybe someone can then a) Recreate the error b) Come up with a reason or solution Thanks anyway for your observations and recommendations, but the problem is not clouded by toplevel forms - not yet anyway! Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rafael Copquin Sent: 19 March 2008 11:19 To: profox@leafe.com Subject: Re: VFP9 Wierd Behaviour Did you check the event firing sequence? Perhaps when you are instanciating the other objects called from the load event in your base class, you inadvertently fire an event that occurs either in the object called or in a top level form. Especially, if you use a background top level form to launch a menu and from that menu you launch the rest of the forms in your app (showwindow = in top level form), you are, somehow, bypassing the default code at some point. This happens because in that scenario the top level form is always called by the deactivate of the form in question. It acts as the higher point in a pyramid. You go from your form to the top level and from there to the object called and back, etc. The suggestion to use the scope resolution is a good one because it goes directly to the code you want to run, while dodefault() runs the code in all the classes and subclasses that precede it. Rafael Copquin ----- Original Message ----- From: Dave Crozier To: [EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 7:08 AM Subject: RE: VFP9 Wierd Behaviour Alan, That seems to work fine, however it is a little worrying as to WHY DoDefault() sometime barfs. I'll give it some more testing first to see if it falls over. Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Bourke Sent: 19 March 2008 09:37 To: profox@leafe.com Subject: Re: VFP9 Wierd Behaviour Dave Crozier wrote: > thought I would ask around to see if anyone else has had similar > experiences. > > Don't recall ever hitting this one Dave. Maybe try using scope resolution (::) to run the parent code rather than DoDefault() ... [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
