Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxtools
Message
From
03/08/2000 20:21:28
 
 
To
03/08/2000 17:41:11
Franz Mueller
J. Schuh Ges.m.b.H.
Kirchberg, Austria
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Title:
Miscellaneous
Thread ID:
00400193
Message ID:
00400804
Views:
18
Thanks one and all. Excellent answers guys. And thanks Franz - that should nail it.

>I can confirm this bug. You can resove this with the following few lines
>
>-----> snip <------
>*
>* don't display the error message "API Call Caused an Exception"
>*
>DECLARE _fpreset IN MSVCRT20.DLL
>_fpreset()
>
>RETRY
>
>-----> snip <------
>
>I have put this code to my errorhandler and since this time, everything is perfect.
>
>Franz
>
>
>>On occasions my users get an error 2028...
>>"API call caused an exception."
>>
>>It invariable occurs just after a print job, that might switch the default printer, where I call the Foxtools Words() function shortly afterward.
>>
>>I can work around it by running this code just before the error would normally occur.
>>
>>
onErr= on('ERROR')
>>on error *
>>words('abc def')		&& avoid "API Caused an exception" error
>>on error &onErr
>>
>>Once Words() errors it runs fine the next time. Very weird! Has anyone seen this?
>>What the heck has Words() got to do with printing??
Previous
Reply
Map
View

Click here to load this message in the networking platform