Replies

I didn't say all the code went over without change. However, as far as setting try-catch blocks, how tough is it to look for an on-error goto and change it to a try-catch if you wrote it right to begin with? More importantly, VB6 and VB.NET are different animals. NET is fully OOP-compliant while VB6 isn't, so why would you not expect some editing? I agree, if you don't intend to take advantages of the enhancements to the language, especially the web stuff, just stay where you are.

"More importantly, VB6 and VB.NET are different animals. NET is fully OOP-compliant while VB6 isn't, so why would you not expect some editing?"

That's been my point all along. VB.Net is *not* an enhanced VB 6; VB.Net is a different beast altogether, trading off of VB's name and reputation.

...And it isn't just "some editing," the software *architectures* between those two languages are different. So you aren't just talking about "some editing" of code, but of fundamental *design* changes...something that should be dealt with prior to coding for OO systems, not put together after the fact as migrating exisitng VB 6 projects over to VB.Net demands.

...Unless you want a lousy Object-Oriented system, of course. In which case, who cares about design or class exercising?!