>But isn't the essence of the product to compile VFP code into .NET modules?
>
>That's part of it, but it's not the greater goal- any more than placing shrouds over furniture is the goal when you paint a room. It's just part of the process. The main intention seems to be to provide a NET 4GL that makes data work really well. In this respect, SQL is SQL and VFP "code" is no longer anything except a vehicle. It's not the "cause" and by itself it's not particularly useful unless it meets the data goals. But it's not a bad choice because it does have proven data features and a pool of early adopters. Etc knows these realities and they've already made enough changes that you might give the code script a completely new label. IMHO that's good, because as soon as you say "VFP," people lose focus and say "ewwww, I don't want shrouds on my furniture" as if that's what it's all about.
>
>Apart from code, Etc seems to be focusing on the UI too, converting VFP forms to WPF or Silverlight. They're not the first: the first attempt I saw to convert VFP forms automagically (to dHTML) was by Rick Strahl, while Marcus Egger once began promoting a product called Voodoo with similar purpose just before he made the switch to NET. This is cool, but the really clever part of Etc's attempt is NET-ifying the data part IMHO.

Not to be cynical -- well, not TOO cynical ;-) -- but the really clever part IMO is keeping people's interest this long with horribly missed target dates and amateurish marketing.