Aside from the technical issues, you might cost out the various options, especially if you are all currently trained as VFP programmers. You can add in training for the new system, new licences, possibly new employees, lead-in time (which costs) etc.

>Hello All -
>
>I don't want to make this a long, long post, so I will try to sum up the situtation.
>
>Overview: The head of IT at a medium size company in charge of an old FoxPro mission-critical application needs to determine the next plan regarding the application. The business (Insurance) is actually quite complex, and the current application was written by clowns how should not have been allowed near a keyboard (horrendous database layout, extremely poor code, etc.). He hears/reads all these great things in the papers and trade magazines (btw, he is NOT an IT guy by training/experience... he's actually from an Accounting background), about VB, Java, etc., and never sees anything about Visual FoxPro. At this point he figures Visual FoxPro is dead, "no brainer" to move to something else (even though his developers--if you could call them that--will be lost!
>
>What information (books? Articles? Etc.) do any of you know of that could help this guy realize that some very big Fortune 1000 firms still use Visual FoxPro successfully, and that he should at least consider a 1-2 year major "fix-up" of the existing application rather than a multi-million dollar 5 year rewrite?
>
>
>________________
>_____/ Regards,
>____/ al
>___/
>__/
>_/
>/