VB type

[Daminc]

Hi everyone, things are coming along slowly but surely with regards to learning VBA to thew point where I'm considering learning VB. However, I see things such as VB6 and VB.Net and I wondering how much difference is there and which, if either, would be best to focus on to start with.

Any advice would be appreciated.

Cheers

[Bob Phillips]

Depends upon what you want to do. If you want the development environment of
VB with the familiarity of VBA, stay with classic VB. If you want to place
yourself along the path MS are pushing, go with VB.N et, but it is a
different paradigm.

--
HTH

Bob Phillips

(remove nothere from email address if mailing direct)

"Daminc" <[email protected]> wrote in
message news:[email protected]...
>
> Hi everyone, things are coming along slowly but surely with regards to
> learning VBA to thew point where I'm considering learning VB. However,
> I see things such as VB6 and VB.Net and I wondering how much difference
> is there and which, if either, would be best to focus on to start with.
>
> Any advice would be appreciated.
>
> Cheers
>
>
> --
> Daminc
> ------------------------------------------------------------------------
> Daminc's Profile:
http://www.excelforum.com/member.php...o&userid=27074
> View this thread: http://www.excelforum.com/showthread...hreadid=516871
>

[Daminc]

According to your advice I shall go with VB6 then. Do you know if this will this be affected by future compatibilities or any other possible problems?

[Daminc]

Another thing I have to consider:

According to this article: http://www.thescarms.com/VBasic/VB6vsVBNet.asp

This article describes some of the many differences between VB6 and VB.NET. Much of the current VB6 code base will not run under VB.NET due to changes in VB.NET's syntax and language, its use of the new common runtime, and its switch to WinForms from the VB6 form model.

Visual Basic.NET includes an upgrade tool to assist in converting VB6 projects to .NET.

It seems like VB.Net might be the way to go as it provides a tool to convert from VB6 which may help cover a wider spectrum of coding options....I hate microsoft . Why can't we just stick to one format

[Bob Phillips]

Don't even consider the VB6 to VB.Net converter yet, it is rubbish, needs
lots of work.

--
HTH

Bob Phillips

(remove nothere from email address if mailing direct)

"Daminc" <[email protected]> wrote in
message news:[email protected]...
>
> Another thing I have to consider:
>
> According to this article:
> http://www.thescarms.com/VBasic/VB6vsVBNet.asp
>
> > This article describes some of the many differences between VB6 and
> > VB.NET. Much of the current VB6 code base will not run under VB.NET due
> > to changes in VB.NET's syntax and language, its use of the new common
> > runtime, and its switch to WinForms from the VB6 form model.
> >
> > *Visual Basic.NET includes an upgrade tool to assist in converting VB6
> > projects to .NET.*
> It seems like VB.Net might be the way to go as it provides a tool to
> convert from VB6 which may help cover a wider spectrum of coding
> options....I hate microsoft . Why can't we just stick to one
> format
>
>
> --
> Daminc
> ------------------------------------------------------------------------
> Daminc's Profile:
http://www.excelforum.com/member.php...o&userid=27074
> View this thread: http://www.excelforum.com/showthread...hreadid=516871
>