Again agreed, .Net is comming along. If .Net versions are 2-3 years apart I can easily wait a couple more versions. VFP never ruled the waves (maybe a bit back in 1989-91) so not much has changed. If I were just starting out, I would have chosen .Net or Java for the same reasons many others have.


>IMO .NET 2.0 is pretty darn close to ready for prime time.
>
>I really don't want to get drawn into any tool wars, since I don't look at it that way in the first place. I have liked FoxPro for a long time and now I like .NET, too. My only comment here is that if you think VFP is going to continue to rule the waves for a couple more versions of .NET, hmmm, I don't know about that. It has a whiff of obstinate denial to it. Nothing personal, at all -- you are definitely not one of the flamers or hotheads here -- just my sense.
>
>
>>Hi Kevin,
>>
>>It's good to hear that things are improving in the .Net arena, looks like it will be quite powerful once it matures a couple more versions. I think it's great that you and others have made the jump from VFP to .Net because I won't have to jump through quite as many hoops when I decide to because I will be able to draw upon knowlege from the community.
>>
>>Bob
>>
>>> I was talking about heavy local data massaging and XML and ADO recordsets don't get me excited.
>>>
>>>Hi, Robert...
>>>
>>>Just a note, ADO.NET datasets are much more powerful than ADO recordsets.
>>>
>>>Kevin