1998-2003, converting a medical claims system from mainframe/COBOL to Windows/SQL-Server/C++. We normally did not need to read the COBOL, but every now and then we would need to compare the "old requirements" vs what the COBOL was doing vs what the actual business needs were. If the "old requirements" docs still existed....

While five C++ programmers were converting the system, two COBOL programmers maintained the system dealing mostly with Y2K issues. Two VB programmers worked on side projects that sometimes interfaced with the SQL/C++ system we were creating.

and basic was 99 lines.

Would have been easier if I had my i-pad.

and from DB2/VSAM over to MS SQL Server -- About 10 years ago.
Data migration was done with DTS and then SSIS later in the project.

VB.Net and C# are really not that far apart if you understand the framework. I would stick to the C++/C#/Java syntax... VB is still dying a slow death.
PowerShell is becoming very popular across all of Microsoft's Server products. It's like the new/better VBScript.

... but I think I would be fighting a now entrenched VB culture. COBOL system I inherited was written in 1991, and although it has been added onto, there was been no attempts to overhaul the system. Write it and leave it in place is the tendency in state government.

Hell, there are thousands of VB6 applications still in production. I've worked with both C#.NET and VB.NET, and they aren't all that different. The syntax is different, but that's about it - a .NET app is a .NET app, no matter which flavor of language was used to build it. There are a ton of applications written in VB.NET, and the beauty of the .NET system is that it lets you extend those applications with whichever .NET tool you prefer.

Ironically, C# really owes its existence to Visual Basic. In their heyday, VB 5 and 6 were the fastest and easiest ways to build business applications. The "real" programmers who worked with C and C++ (and some other, archaic languages) were dismissive of the VB language, but when Microsoft built the .NET Framework, they used a Rapid Application Development model like VB to launch C#.

One of my coworkers does a lot of VB6, and some it I could probably do with AutoIt.

There is a push to try and replace all our VB6 code with VB.NET

ORLY???

I guess losing that lawsuit to Sun had nothing to do with it.

...and the other .net languages all compile to the same thing, so it doesn't matter which language you use with it. .Net is awesome for Windows programming.

VB was my first language, it will always have a special place in my heart, especially control arrays.

Even though VB.NET and C# essentially compile to the same thing. I agree that VB is on the way out, has been for ten years. A lot of people cut their teeth on that language, myself included.

Never did any COBOL. Sounds like fun debugging old code though, I got really good at debugging other peoples code when I tutored programming in college.

But my first cousin (who's 25 years older than me) had the job of updating a lot of legacy stuff back in the early 2000's. It was the first time I'd actually seen COBOL, as I was just starting out as a programmer in those days.

With all due respect to the late great Commodore Grace Hopper, I find the language too tedious to bother with, but then again, we wouldn't have made the leap to compiled code so early if she hadn't been a pain in the ass about making it happen. My favorite quote of hers is "It's easier to apologize than it is to get permission."

That said, when I was in college I was already a computer geek (I'm older than you by a few years). The CS students all came to me with their COBOL, Fortran and Pascal listings (the two of which I DO know well). If it was COBOL, I would just flip the 2" listing upside down and peel down the back page to look at the code. The format statements have nothing to do with logic errors, most of which were simple (like initializing a loop with 1 instead of 0).

If you're considering jumping to VB, I would recommend you go with C# instead. It isn't as straight forward a leap, but it will have greater longevity. I still consider VB to be a pro-typing language. As much as I resisted moving from C++ to C#, I do have to admit that the latter fits well with the VS10 environment and has some advantages such as out-of-scope memory management.

One last piece of advice. Only concentrate on the core routines which translate directly. Use your talent and imagination to create a more up-to-date interface and add new features at will. I loved WordStar, but I wouldn't want to be stuck with that now (sorry for the analogy, but it might not be far off).

but just last year I had to use my knowledge of COBOL to convert some data related to a criminal investigation.

Was quite a trip down memory lane.

if you write "spaghetti code" like my supervisor (during the time I was writing in COBOL) did. He'd get out his "GOTO" shaker and sprinkle liberally throughout the code.

My wife wrote in RPG for 17 years and then lost her job. She just wants to code - no analysis. We are in Milwaukee, Wisconsin area and wonder if there is some good fit for her. Any ideas?

However, I did find a couple of hits on Indeed.com

http://www.indeed.com/jobs?q=rpg&l=Milwaukee%2C+WI

I'm back with the same firm but in a different job, outside of the mf dev group. That's been moving to India and now China. Of course.