>
This is one of the very reason why I wish VFP is a full .NET tool and not just for creating Web Services. Marketing VFP as it is today will only be good inside VFP community and IMO no matter how I think of it, it will never impact the external community. But then again, it's an exercise in futility...
>

VFP .NET would be a waste of time. You would have to leave the local data engine behind.. As a result, you would be left with VB .NET - essentially. Take away the core language parts of VFP - and you bascially (no pun intended) have Visual Basic.

If you are looking for VFP .NET - it already exists - it is called VB .NET. Alan Griver (YAG) is part of that team and you can bet good things are going to happen. YAG is one of the smartest people I know (both on a technical and business level).

There is a tool that is going to need to input of a lot of talented people. I see many VFP developers making valuable contributions in that arena. How about an application framework in VB .NET???? VFP developers know a thing or two about that process.

As for the other comments you made, I think they hit the mark...