Gaylen, I agree to some extent. I actually cringe a little every time I hear they're adding a great feature from VFP to .NET. On the other hand, maybe VFP is getting more respect around MS now? And maybe all this respect will lead to another version? Also, I think some of the lack of focus on VFP from MS was due to the fact that a separate DB was not needed and thus didn't require a SQL Server. Based on this it will be interesting if they actually do put something similar in .NET because it would pose the same problem...
>>>I agree. And don't get me started on how great visual inheritence is in VFP but is lacking in VS. :) The good news on the topic of VFP features for .NET is that I'm spending more time than ever demoing VFP 9.0 features to various teams within the Visual Studio groups. I was even told by an Microsoft executive earlier this week to keep it up and to be even more agressive about it.
>>
>>Wow! This is a hell of good news!
>>
>>Keep spreading the gospel! 8-)
>
>How much good news is it if you have no designs to change to .net anytime soon? Where is the benefit to the pure VFP9 developers? I appreciate all the new functionality in VFP9 and congratulate Ken and his team for their efforts but how does porting VFP to .net help me and why should I be excited?
>
>Thanks
>Gaylen