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

I don't think that is the point. MS SQL server is very, very mature. However it is not a development tool like VFP. Its server software to serve data to external processes in SET ORIENTED chuncks. It takes other front end software to provide a GUI to the user. VFP has all-in-one.

VFPs strength is that it allows for direct access of data in a RECORD ORIENTED approach. You basically can write a program using a few BROWSE FOR commands which allows the user to search, modify and store their data within only a few lines of code. Now try doing that in any other solution. Sure implementation of new builders, wizards and other 3rd party framework solutions might also get the work done, however it does not come out of the box.

Bottom line, is that if you're talking data, VFP still is king. Not from a storage pov (SQL server is way better at it), but just from the pov of accessing and manipulation side of it. Most of the times it only takes one or two commands to get at the data you need.

Walter,



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