Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
The History of FoxPro
Message
 
 
À
23/10/2001 12:06:33
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00572102
Message ID:
00572946
Vues:
22
Hi Fernando,

Andrew Forber last time visited UT on April 26, 1999. Did you try to email him?


>Hi Andrew,
>
>We are gathering information for the writing of the History of FoxPro, and Rick Bean told me about a solution you presented (please see below Rick's message for details) to fix the Divide by Zero ploblem in FoxPro. We are assembling the FoxPro timeline, and found this event to be a relevant one, deserving to be mentioned in the timeline.
>
>I ask you, please, if you could give information about when that happenned (to fit in the timeline), versions of FoxPro affected, and other details you wish.
>
>Thanks,
>
>Fernando
>
>=========================================
>
>Rick Bean wrote:
>
>First Andrew is a member (#27965), so maybe you can get the details from him. The way I remember it, he was among the first to discover the Divide by Zero problem and because he needed an immediate fix and had the talent, he figured out where the problem was, and created both a .PRG and later an .EXE that patched the FoxPro Windows files. His solution is unique in that it will fix any version of FoxPro Windows 2.5 or 2.6 (and a number of other programs that used the same technology that caused the "real" problem). Shortly before MS released the "official" FoxPro Windows 2.6a only patcher, they requested that Andrew withdraw his technically illegal version from circulation - and he did! If you do a search on DZPATCH, you can still find a number of places that still offer it, because its the only solution for code that simply can't be upgraded to FoxPro Windows 2.6a. Some have suggested that without Andrew's "push" by publishing this code, MS may have never provided a fix (or at least
>waited a lot longer) - after all they really wanted you to upgrade to VFP 5.0!
>
>Rick
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform