> IMHO, if you don't need changes and use of the new features that
> VFP5.0 just stay with FP2.6
> for an app. to really take advantage when moved to VFP it should be
completete reengineered
>
> also if you are moving an app from 2.6 to VFP3.0 (not 5.0) u probably
will gain even less with just moving the app
IMHO The indirect gains of moving 2.6 apps to VFP 5 are important for me as
a fpd2.6 developer.
1. It helps get rid of the DOS environment all the sooner.
2. It allows me to be get comfortable in a radically new VFP while working
with old code that I know well.
3. It allows me test new features one at a time. I like doing things bit
by bit as I am a slow but sure learner.
4. All legacy applications are usable for my business. It's life is
further boosted.
5. Each legacy module is updated bit by bit although it will sooner or
later require a major uplift.
I am still able to support the old apps in VFP without having to work
with fpd.
Working with two development tools is very frustrating. Especially
because the editors are diff.
Very often I write new features in VFP that I can apply to FPD but it
is such a bother to switch
and maintain two code sets of utilities.
6. My delopment team is small.
I am able to learn the new oop without having to be productive. I can
always use the old style code
if I get into problems. By being total in VFP I am forced to learn the
new stuff and apply them as I go along and yet be productive.
7. There are lot of other reasoning I'm sure. They just do come to mind of
hand.....
Regards Gan
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement