>>>>>It would? Maybe there is something fundamental I am missing about eTecnologia's product. I thought it was a tool to compile VFP code to .NET. (Is that incorrect?) I don't see how that makes VFP any less deadend.
>>>>
>>>>Is this your personal attitude as a developer?
>>>>
>>>
>>>I'm not sure I understand the question. Can you please elaborate so I know I'm answering the right question?
>>
>>I think what I am getting at here is when you look at FoxPro + .NET as a developer does it seem just as much a deadend as FoxPro alone?
>>
>SNIP
>>
>
>Maybe a little less. But I take it the same way I would take an announcement that an auto company is going to come out with a Studebaker hybrid. The hybrid part would be trendy but it's still gonna be a Studebaker.

Once ago a time, not so long ago (12 years) , I was ask by the management if we excepted to continue development in VFP. I replied to them; We have already made the transittion and are using Visual Studio. This was during VFP 6.0. As all know it was apart of VS 6.0. The application was manily written in Fox, but use several internal COM objects and external support applications developed in other VS languages (C++, VB). They look at my statement as a releif. "Wail, Good job!". The repretation is only where people place it. Most client have two consunes: what do I get? and What will it cost me? If the result is what they desire and it occurs under their expected budit, they are happy. The true problem does come in the support area. I agree with others that that those with VFP experience are becoming harder and harder to employ. We are there, but the lack of those willing to continue to push the need seems to be falling.

There are several languages consider obsolete that have already been deveoped in a .NET language. WHY NOT VFP? Is Iron-Pyton a main-stream language? Or Ok, maybe. But I do not see much call for them on the Job board? Why can't VFP rise from it's aches like a Phoenix.

There is a name; Phoenix.