>>>>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've got experience in VB and Java - which means I can survive in C#. These guys are coming from a strictly Access point, so either will be new for them. I think people tend to lean towards VB is because it's a little more 'English-y' and therefore a little more comfortable for them. I think they're all lost in stupid periods :-).
>
>
>I have always thought of any version of Basic as self centered. Me this, Me that! :)

I go back to when every statement had to start with 'LET' - and I figured out real quick that any programming language that required me to ask permission on every line was NOT a language for me.

LET X=5 No, dammit, I'm TELLING you that X = 5, not asking you.

But then again, I always want to get this overgrown TI-59A do what I want it to do and do it as quickly as possible :-)