I do believe that .NET has a lot of very interesting a worthwile attributes.

However, I do seem to recall that the transition from FP to VFP resulted in the loss of something like 75% of the Fox developers. The OOP paradigm shift was apparently too much for a lot of folks.

Now in the .NET environment I see the following things needing to be learned:

C# or VB.NET - replacement for VFP language
ADO.NET - replacement for VFP cursor
Crystal Reports - VFP includes a report writer
SQL Server/Oracle - you can get by with VFP local DB engine

Seems like a lot to learn for most persons. Wonder what the fallout rate will be with .NET?

>>>Bah. Have you run any .NET apps on Windows .NET server or IIS6?
>>Yes and your point is????
>
>Whats your favorite new security feature in Windows .NET Server?
>
>>You are over-simplyfing things a bit...
>
>I don't think I am. IIRC, I repeatedly suggested that it takes more than a nice IDE and framework to make a sucessful Web service platform and you said something about but developer productivy is how IS manager's make their decisions.
>
>>VFP 3 was a complete paradigm shift from Fox 2.x - period...
>
>And VS6 to VS.NET is a minor upgrade? The new ASP.NET, ADO.NET, CLR, IDE stuff isn't as drastic as FoxPro2 to VFP3? How about the .NET Framework taking over the responsiblity that used to be up to languages, or how about VB becoming fully OOP? That stuff is a "logical" progression making all the new stuff "proven"?
>
>You've fooled yourself into believing.