I highly suggest you use VB .NET because all future VB version will be based off .NET. It's also newer so it should be better but you never know with mircosoft behind the wheel.
I highly suggest you use VB .NET because all future VB version will be based off .NET. It's also newer so it should be better but you never know with mircosoft behind the wheel.
But on the other hand, there are thousands upon thousands of VB6 programs out there already, so people need VB6 programmers to maintain what they already have.
But on the other hand, there are thousands upon thousands of VB6 programs out there already, so people need VB6 programmers to maintain what they already have
That is true, but you could also just port it to VB .NET and maintain it from there, on a new OOP standard. Like I should say that though because I don't use the OOP features of VB .NET not yet anyway.