ranga_kartik
asked on
focpro 2.6 divide by error in windows sp sp2 professional
Hello
i have faced the same divide by zero error when running foxpro 2.6 in windows xp professional SP 2.
For that i have donwloaded the path_26.exe from microsoft site. after extraction, i found 2 files one path26.exe and readme.txt
as per the text instructions and found the mentioned errors in braces. Since i encountered these errors i dint go ahead executing other commands. Please help me to solve this.
CD C:\FPW26
ATTRIB -r FOXPROW.EXE ( ran successfully since no message is printed )
ATTRIB -r FOXW2600.ESL ( cannot find the esl file )
PATCH26 FOXPROW.EXE ( PATCH26: error : incorrect FoxPro 2.6a file size : C:\FPW26\foxprow.exe )
PATCH26 FOXW2600.ESL
ATTRIB +r FOXPROW.EXE
ATTRIB +r FOXW2600.ESL
ASKER
do we need to download all the files provided or any specific files are to be downloaded ?
Download the Readme.1st and follow instructions.
ASKER
what is meant by distribution kit and how should i know that my software is with or without distribution kit ?
ASKER
there are so many patches for different scenarios. Which patch should i take whcih specifically solves this divide by error problem ?
If you'll find FOXW2600.ESL on your computer then you have distribution kit.
The divide by zero problem solves the path_26.exe which you already have. This patch is not included on above Microsoft web page.
The divide by zero problem solves the path_26.exe which you already have. This patch is not included on above Microsoft web page.
ASKER
well i hae searched the esl file and dint found it so i guess it not a distributable kit. So now as per the link you have provided, i have downloaded all the files. So should i patch all of them to solve this divide by error problem. Suggest me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have recieved the message after running DOPATCH.bat saying
" All files are up to date. "
So from here do i need to run the patch_26.exe ??
If yes do i need to execute all the commands set mentioned as per the readme.txt
ATTRIB -r FOXPROW.EXE
ATTRIB -r FOXW2600.ESL
PATCH26 FOXPROW.EXE
PATCH26 FOXW2600.ESL
ATTRIB +r FOXPROW.EXE
ATTRIB +r FOXW2600.ESL
or
ATTRIB -r FOXPROW.EXE
PATCH26 FOXPROW.EXE
ATTRIB +r FOXPROW.EXE
since my software is not a distributable kit. Please help me solving this.
ATTRIB -r FOXPROW.EXE
PATCH26 FOXPROW.EXE
ATTRIB +r FOXPROW.EXE
is enough.
PATCH26 FOXPROW.EXE
ATTRIB +r FOXPROW.EXE
is enough.
ASKER
Thank you very very very much.
You are welcome.
And please if all questions were answered accept one of the answers as a solution.
BTW, FoxPro 2.6 is reliable but obsolete tool. You should look for some upgrade to Visual FoxPro which will introduce the Object Oriented world for you.
And please if all questions were answered accept one of the answers as a solution.
BTW, FoxPro 2.6 is reliable but obsolete tool. You should look for some upgrade to Visual FoxPro which will introduce the Object Oriented world for you.
ASKER
can we do the work of legacy foxpro 2.6 in visual fox pro ?
Please post any other information on that which would be very helpful.
Please post any other information on that which would be very helpful.
Yes, Visual FoxPro is backward compatible and FoxPro for Windows applications can run under VFP. Some minor changes are necessary, of course. But if you set _screen.Themes = .F. in VFP then it works obviously.
VFP has different way of forms creation. It does not have Screen builder known from FoxPro 2.6 but you may still update 2.6 screens in FoxPro 2.6 and run just the .SPR files in VFP until you port/convert all FPW screens to their VFP equivalents.
To create a form is much easier in VFP than in FPW. And if you create form class(es) then you even don't need to place any piece of code into the form and it will work on any table in your application.
Reports are easily transferable to VFP without any change obviously.
FPW is a good start to learn xBase language but VFP will allow to do much more.
VFP has different way of forms creation. It does not have Screen builder known from FoxPro 2.6 but you may still update 2.6 screens in FoxPro 2.6 and run just the .SPR files in VFP until you port/convert all FPW screens to their VFP equivalents.
To create a form is much easier in VFP than in FPW. And if you create form class(es) then you even don't need to place any piece of code into the form and it will work on any table in your application.
Reports are easily transferable to VFP without any change obviously.
FPW is a good start to learn xBase language but VFP will allow to do much more.
Then reapply the Divide by zero patch.