Thanks for taking the time Mario

Mal

>So, follow you own conclusion: Take the easy route, vfp, take a look at .NET.
>
>Sound like none but in the end is your decision, and no a easy decision: is the decision for risk in be "legacy" against "bad user perception" or "fail to deliver" or risk in "safe for future" to "???".
>
>Put in balance what you want, then list + and - on .net&vfp, then see how hard can be the task of done the app and the time expected. If large time, then start to consider .net, if short take in account that next OS is for 2006/7+ so is away (the os that take real advantage of graphic power, then .net can be fast, i imagine), and maybe a update on .net for get a basic performance. Visit MS site, read about .net, take in account your customers, your time..and pray for decided rigth.
>
>Have a foot in both camps, that said in borland newsgroups...