Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Divide by zero error.
Message
 
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00171867
Message ID:
00171915
Views:
25
Hi Ed:

Thank you very much for you very helpful response.

Sincerely, Igor Gelin, System Developer.


>>Hi
>>
>>Recently I changed my computer to Intel 450 Mhz with Windows NT.
>>Now when I try to run FP 2.6 for Windows I get strange error "Divide by zero". What should I do to make it work? By the way, application written in FP 2.6 for Windows works fine.
>
>John petersen is going to bitch about this, but you might want to take a run out to Abri's Web Page. They have a patch that will addres this and other problems. John will tell you that this may violate your licensing agreement with Microsoft. Since MS hasn't done anything about providing a fix themselves, you make your own decision - violate the licensing agreement on a product that MS won't provide support for and don't complain to MS about it, and don't distribute the patch on a commercial basis if you do find that it works for you.
>
>Disclaimer The following is my opinion and is not official, or even unofficial, UT policy. it is not sanctioned by Microsoft or UT. Flames should be directed to an appropriate bit bucket. UT is not responsible for my beliefs, and I didn't check with them before writing this.
>
>Microsoft's recommendation at the moment is to switch to a version of VFP and rewrite or port your app; this is not a solution AFAIC, since for Win3.x environments, it would require the addition of the (now unsupported) WIN32S environment, which is notoriously unstable and doesn't provide full Win32 compliance and using VFP 3, or switching all your systems to a Win32 platform like Win9x or WinNT to use a later version of VFP. This doesn't provide a realistic fix for the problem for most people, since it doesn't help if you don't have source code, or aren't experienced programmers with plenty of time to deal with the foibles of moving an app from FPW to VFP, especially where have a perfectly stable FPW app that you'd rather not break by porting it to VFP, and don't plan to extend in the future.
Igor Gelin
Database Developer
Previous
Reply
Map
View

Click here to load this message in the networking platform