Is SQL Server immature technology? Are there not easy ways to use it in .NET apps?


>That is really the key issue for many. Yes, we knew VFP had a short life ahead of it. We saw it coming. That doesn't make it any easier for some. However, even with MSFT's HUGE investment in .net and the fact that it does supercede VFP in some aspects, it is not a mature data-driven development tool as VFP is. Developers are being offered a non-mature data handling tool to replace a proven, mature, data-handling tool. Hopefully, .net will excel in this area as well when support for VFP ends. VFP is mature and developers can continue to use it for years where it is the best solution. In reality, it may be that developers are forced to used mixed solutions to meet requirements (which in fact occurs today anyway). MSFT does not have to give us anything other than a notice. I do not expect anything else. I would, however, like to see a REALLY GREAT alternative not just an acceptable one.
>
>
>
>>Tracy,
>>
>>There are already a significant number of other vendors supplying products to run on the .NET platform. You don't need to use VB.NET or C# to do .NET. Ethnologica (?) seems to be one company who is willing to provide a VFP like language on the .NET platform. Now I'm personally not sure whether this is what I'm looking for (I'd like to look for something better, not equivalent to VFP), but it certainly provides a different approach to strict type implementations on the .NET platform.
>>
>>As with the increasing maturity of .NET, things will get better, though I still have to see how well .NET stands in lets say 10 years from now.
>>
>>Walter,