>>>>thanks Tom, I'll give them a look
>>>
>>>Just a suggestion: Consider C# over VB. We built many critical apps (for Toyota and General Motors) using both. Our job was to keep the production line running (automated and robotic) and interface with hundreds of suppliers, engineering, production and quality control. Some VB apps had problems, even though they gave no errors during builds. A few months down the line they failed, because of a coding problem. We had no problems with C# apps.
>>>
>>>As I have said before, as long as Bill Gates is associated with Microsoft, there will always be a product that is called Basic. It may not be particularly good, but the sales and marketing people will push it. :)
>>
>>Again, thanks for the info - I'm a contractor here so the best I can do is pass forward the information. I think one of the guys would love C#, one of the guys is pushing VB and the others don't care one way or another.
>
>I'd echo the advice about C#. I started in VB since it looked more familiar as I moved from VFP and still maintain and expand some big apps in it, but I think learning C# is a must, if only to be able to take advantage of the books and samples that are now almost exclusively in C#. I have never had a problem with VB but I I could not read and write C# I would have had a big problem. For contractors I think fluency in C# is a must as VB demand decreases steadily relative to C#.
>
>( I might add that for a professional who knows VB learning C# should not take more than a day. It really isn't a big deal to make the switch. )

I'm not sure about a day but I'm sure we agree that the big part of the learning curve is the .NET framework, not language syntax.