>VFP talent pool was never really abundant. You take person and then you teach the person to do what is needed. What is foremost request in my books is some intelligence, grain of common sense and propper atitude twd work
>and responsabilities.
>
>If top management come tmrw with brand new project, I wld still do it
>with VFP, because that would produce results in shortest possible time
>and would fit right away within already established integrated system.
>(I am no software vendor/company). What I put lately on my IT agenda is research of alternatives. So far I did not spot product that would fit in this kind of environment/requirements.
>I don't know what is happening in corporate America, but here we cannot afford timewise projects which take 1-2 years to complete. We cannot and we don't work this way. There are no waist budgets (nor time) to spend on hiring and managing/administrating teams of developers, while commercial software vendors cannot fit the bill because they are clueless as for nature of our business. It simply needs highly effective inhouse team. We implement huge systems at our new or acquired ventures (whole shipping suite, integrated invoicing, accounting etc) in a matter of few days, and by few emails sent from top above. Typical implementation time is from 2 days to 2-3 week max.
>So what would you choose if you lived in this kind of environment ?
>Would you (as Kevin honestly did) still choose NET, based on your personall
>preference ? Would you be able to cope with these kind of deadlines ?

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...

>As you can guess VFP is still ultimate solution in this case. As for future
>we will see. I am keeping my eyes/mind open, sincerely hoping that NET will
>mature faster then it seems and/or that some other xbase tool with emerge as
>effective VFP replacement for the future.


>
>Right now, even with EOL announced VFP is still my #1 :)