>.NET will not be required to use or develop for SQL Server 2005.

True, but SQL server DBAs who don't "acquire" a .NET language under their belt will soon be regarded as second rate to those who do. So, by default, the use of SQL server 2005 will "push" DBAs and SQL developers into .NET whether they like it or not - market perception will drive this. By the way, I have no axe to grind as I develop in C# (as well as VFP) and eagerly await SQL server 2005.


>
>>
>>Hiring other developers, a decent # of my clients do care what the app is developed in, we use a SQL based backend (either MSDE or SQL Server) so with the next version of SQL Server, guess what, it's .NET based (of course the t-sql will still run), but the backend being .NET/CLR based will give more of an incentive to learning more and more about .NET. Not a biggie, accepting change is an important part of the development world, I'm just at that point that I'm realizing I need to say goodbye to my long time pal, VFP. I'm going kicking and screaming of course and I've been thinking it for about a year and a half now, but the MS position of not marketing, not complaining, no changes, dying on the vine is what has helped propel me to make that change.
>>
>>But, you're right that VFP is not only not that bad, I think it still kicks butt..