Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Vfp has caused an exception 10h in module vfp.exe at etc
Message
 
To
10/06/1999 10:11:29
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00228374
Message ID:
00228393
Views:
19
>First of all, thank you for all the past help and I hope you can be of as much use to me this time. When I try to print a couple reports from an accounting package I have written, I get the error VFP has caused exception 10h in module vfp.exe at
. The address bounces between two addresses, but they always repeat. Through Microsoft's tech net, I found the error and some possible solution though it claims the error is only in vfp 5+ and I am using vfp 3.0. Also, this all worked until we upgraded the clients machines to win98 from win 95. The win 95 machines still work just fine. Microsoft gave three solutions. Use a windowsprint driver. I cannot because then a special font we have created for their logo doesn't work and bit maps are too slow. The second solution is to turn off the numeric coprocessor. When I do this on my test machine, win98 has problems though the program works. Final solution is to use a Visual c++ call to reset the numeric coprocessor, but it
>doesn't do anything. For those unaware of what causes this, it is caused by a divide by zero after having called a non windows printer driver. Well, I cannot find a divide by zero in the report form and there are not any in the code. My question for everyone is if they know a work around for this problem or if not, do they know a way to view all the code in a report or to search through the code in a report so I can try to locate this divide by zero. I will be upgrading to vfp6.0 in about a month, but this is listed as a known vfp6.0 problem as well so that does not seem to be the solution. Any help would be appreciated, even if your not sure its valid. Thanks in advance,

Hi Jason,

Assuming that this is the divide by zero error, be aware that VFP 6.0 SP3 addresses this by making VFP more fault tolerant of printer drivers that re-set the numeric co-processor.

Is this really a VFP problem, however? IMHO, it isn't. The underlying cause is the manufacturer (most often HP) failing to follow the specs as outlined. This is why MS recommends a Windows driver for the problem.
George

Ubi caritas et amor, deus ibi est
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform