Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Upgrade considerations
Message
De
29/04/1999 02:06:38
 
 
À
28/04/1999 14:08:50
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Divers
Thread ID:
00213087
Message ID:
00213325
Vues:
27
Hi John,
A bare bones approach? I'd be looking to taking the .prgs, .sprs and the mprs and converting on a straight code basis.
Zero - or near to it, re-engineering.
Later if he (the client) wants screen mods then can sneak some real VFP in there based on original screens as required.
Dave

>Hi All.
>
>Advice sought. I have run into a situation where a faily complicated FPW2.6 application needs to be converted to VFP6. The original developer cannot be contacted. There are no design documents or analysis materials. The project contains 40+ screens and 100+ program files (most of which are one procedure wonders). The process owner does not want to invest any time in re-engineering the functions of the application....wants a straight port.
>
>In general, what approach would you all take? I'm looking at, maybe, a functional decomposition and then re-engineer the myriad little PRGs into functional custom classes. Maybe not, though.
>
>Any words of wisdom?
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform