Alan and Rafael, I "think" that I have the problem at least isolated now in that when it occurs and I am thrown into the debugger if I then:
1. Cancel the program from the debugger, the problem will continuously re-appear when I re-run the program again until I issue a clear all in the command window. 2. If I select "Fix" in the debugger and go into edit mode, then cancel out of edit mode without re-saving the form the problem goes away, as if going into edit mode resets everything. The errors/fixes above are regardless of whether I use DoDefault() or call using scoping. I think It must be some sort of timing latency issue when in development mode as funnily enough the problem NEVER arises at runtime - thank God! Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Bourke Sent: 19 March 2008 11:51 To: [email protected] Subject: Re: VFP9 Wierd Behaviour Dave Crozier wrote: > My feeling is that this is a timing issue as Allen suggested. > Try this just before the DoDefault() or scope call. * -- Use Win32 API call to suspend for 1 second. Declare Sleep In Win32API Integer nMilliseconds = sleep(1000) ... or maybe, if you have a dual-core CPU, set the VFP9 affinity to be one or other of the cores. In case it's some bizarre multithreading thing. [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] 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.
