>PJMPI,
>
>If business classes are already in placed, the timetable in completing data development in NET can be closed to what VFP could offer. Sometimes it can be even shorter depending on how you started your foundation in .NET development. If you have a very solid foundation in .NET (components are properly done), you can outsmart yourself using VFP. In .NET, less debugging time would be needed because most of the errors has been trapped during compilations.
>
>In everything, the difficult part is in laying your foundation. Same thing in .NET, the hard part is creating a momentum...


Sounds realistic and probably way to go for
new developers/software shops. (I am not talking about you)

I hv no problem taking challenge and developing such thing (foundation/framework) but question is
why should I do that. I hv done my hardship with VFP and it simply works/pays me back very well.
I don't see (yet) compealing reason to switch to anything else.
Unless you count NET-hype & VFP EOL announcement momentum - as compealing reasons which I really don't.

People without hard investments in VFP can probably switch easier,
where in my case, I really hv to see something impressive out there
and be compealed to adopt it.
Compealing reason/time to switch will be if/when NET (or something else outthere) start *really* outsmarting VFP and offer something substantially better. I wld say 5-7 years from now, situation on the scale might change but rigth now all weights on my personnal scale are still clearly on VFP side.