>>The product seems aimed at those who want to continue writing in FoxPro, just with a .NET target.
>>
>>If you check what eT itself is saying, that is not entirely the case. They (correctly) perceive that their concepts have particular benefits: it's just convenient for us that VFP has the right combination of data and UI that makes it a suitable carrier.
>
>Could you possibly be more vague? ;-)
>
>OK, let me put it this way. Who do you think will be interested in this product other than VFP developers who want a .NET target?

People, like those of last assignment, who have invested lots of money and time into developing a successful product with a large client base. The clients are also hearing of the Fox deadend and are asking when the application will be ready for the .Net stage. Rewriting the application would require 3 years or more, where with eT compiler that could reduce the time to possibly less then a year. Plus add several enhancements that have pledge the application: 2Gig DBF limit as one of the big ones. If there is the ability mix language modules written in different languages (which I believe there is) then migrating the application would be much easier.