Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Exception C0000005 on wait window command
Message
 
To
27/11/2001 09:06:01
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00586253
Message ID:
00586328
Views:
26
Hilmar

Thanks for the quick reply. I don't think lnCount can be the wrong type. The loop looks like this:

local lnCount
lnCount = 0
scan
lnCount = lnCount + 1
WAIT WINDOW 'Working on record: '+str(lnCount) TIMEOUT.2
... more code...
endscan

Also, even if it were the wrong type, why the fatal error and not one trapped within VFP?

As for the timeout, I found slowing this down helped ease some record contention problems (I know it was kludgy but at the time it seemed to help...<s>).

I do agree separating out the str() call my help and I appreciate your thoughts.

-- Larry


>>Hi all,
>>
>>I've got an installed application recently upgraded to VFP7 that has kicked out the following error twice:
>>
>>"fatal error - exception code C0000005"
>>
>>When I look at the line of the "called from" routine, I find the innocuous line: WAIT WINDOW 'Working on record: '+str(lnCount) TIMEOUT.2
>>
>>This line was inserted to slow down a loop that was batch processing some records. The whole thing appears to work 99% of the time.
>>
>>Any ideas what could cause this error intermittently on such a simple line of code?
>
>The command can fail if lnCount is of the wrong type. Separate this into two commands:
>
>
>local lcMessage
>lcMessage = "Working on record: " + str(lnCount)
>wait window lcMessage timeout 0.2
>
>
>Or use trans() instead of str():
>
>
>wait window "Working on record: " + trans(lnCount) timeout 0.2
>
>
>Also, why the timeout?
>
>
>scan
>  wait window "Working on record: " + trans(lnCount) nowait
>endscan
>wait clear
>
Larry Tucker
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform