I've been to multiple .NET programming courses and have yet to find the time to jump into it. One of the problems is that I get back to work where we have huge amounts of VB6 code to maintain under very tight time constraints. We're also in a very closed business environment where data is used concurrently and tables are often opened in shared modes where the users need to see immediately if others have altered data.

The whole .net data access programming structure is geared more for internet usage where you'd never dream of dynamic usage of tables like that. You grab what you need, alter the local copy of the recordset, go back and check for changes from other users, and then make major decisions on how you'd update things. Consequently, the legacy stuff does not lend itself to conversion to VB.NET without a major or complete rewrite. There's no time for that.

I have to tell you that I know the .net stuff is really a programming dream but there's a lot of us feeling awfully betrayed by MS for dropping updates and support for VB6. If you need an application that will never touch the internet and needs quick and dirty functionality, VB6 is really a dream. You don't need to memorize the makeup of hundreds of namespaces or spend hours perusing through help files to find the ones you need. Of course if you're using the tool daily those things come naturally but it doesn't lend itself well to a mixed environment where you're constantly pulling away to deal with legacy apps.

I'll get into it eventually but I may have to change jobs to find the time.

Art