Re the possible timing error what I have noticed is the debugger comes up if I save suspend and clicking go again continues without another error. This is why I think it’s a timing error. I also have doevents before and after the creation of the calendar and that does not help. In my case no dual core so I don’t believe it to be the cause. Allen
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Bourke Sent: 19 March 2008 12: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. No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.21.7/1334 - Release Date: 18/03/2008 20:52 _______________________________________________ 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.
