>
>Fine, you don't. But this has been raised often by lots of people. There's a reason for that you know. It isn't just idle chit-chat or make-work type discussion.
>The DevCon seemed to discuss (as seen from afar) an 'either/or' situation, with the concomitant loss of basically all VFP I/O functionality if .NET was chosen. Of course people would opt OUT of that! Was an option for 2 products, regular and .NET, even discussed? I doubt it.
>

The VFP team doesn't have the resources to do both. It is definately an either/or. IMO, VFP is in a fantastic position, much better than VB.

>I have confidence that VFP as-is will continue to be very productive in a .NET world. But having a full foot in the .NET arena sure appeals to me and lots of others.

And what would be the problem learning C# or VB .Net. Those VFP developers that use SQL Server have learned another language, T-SQL. Nothing wrong with adding something else to the mix. In fact, it will be very useful.