Hi, Claude.

>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...

MSDE and now SQL Server Express are available with no license cost for all the other platforms, and while you have some limitations, for the type of projects they are not enough many times the licensing costs are not so terrible, so I don't think this argument as a very important factor.

My guess around VFP never been very strategic for Microsoft is that it is based on some set of premises and technologies that don't match very much with the ones Microsoft designers were building at any time in the last ten years (and I don't mean any of the two strategies were better, but that they were different paths).

VFP has many features I love, and some things I never liked. I'm happy with the prospect that a very good platform (my opinion) as .NET gets more and more of the good features from VFP. I know it won't probably go as far as most of the VFP community would like, and every one of us have different needs and priorities, but for sure we know that there are many good ideas .NET could steal from VFP, as you said.

Best regards,