>>Why target only VFP developers? Who else would want a VFP compiler at this point? Do you think new people are coming to the language? -- looking around at the available options and saying, "Yup, that's the one for me!" That hardly seems likely.
>>
>>I get what you are saying about the strengths of FoxPro. As you say, there are DOS apps still running and working. But why would those people want a .NET compiler?
>
>I have a client for whom I maintain a DataFlex application. (Anyone remember DataFlex?) I would like to convince them to rewrite the app using a large FoxPro application that I own as a base. I'm worried about the question:
>
>Why would we move from one deadend language to another deadend language?
>
>A VFP.NET would remove that worry.
>
>Peter

I doubt that it would. You'd have a lot of explaining. Our clients (financial firms) won't touch unproven technology so it would be a hard sell for vfp.net.