Tony,

C# is a good place to start in .NET but I feel that when one does decide to make the .NET plunge you need to commit to learning C# and VB.NET as well as the ASP and ADO stuff. One of the features.curses of .NET is that classes written in C# can be instansiated in VB.NET and vice-versa. So when the various tools/samples are developed you may have to deal with either language.

I personally think .NET is a great opportunity and I have already committed to a major project using .NET.

>Hi John,
>This has been one of the most informative and inspiring threads I've read in a long time. It's tempting at times just to throw your hands up and give up on trying to keep up. About the time you think you've started to get a handle on stuff, they go and change it all (or atleast alot of it) again. I'd considered getting into VB6, but it looks like I might be better off looking at C# since I don't have the VB6 bagage to start with. I use to do C and Assembler back in the Commodore days, many moons ago. Anyrate, thanks for the info and keep up the good work.
>
>
>>Seriously, the most important thing is for those VFP developers that want to get into using .Net, is to get into the box as quickly and efficiently as possible. And, if that means the first thing folks do is tinker around with windows forms that tie into VFP web services, then so be it! That may be a great place to start.
>>
>>The old saying goes, you gotta crawl before you walk.