VB vs VBA question
- Thread starter Jaimee001
- Start date
SirJB7
Excel Rōnin
Hi, Jaimee001!
Briefly VB (Visual Basic) is an independent programming language which reached Version 6 circa 1998, and that has been replaced in 2002 by VB.NET (Visual Basic .NET), which is now by Version 10 of 2010, and Beta 11 of 2011 and sooner will arrive Version 11 of 2012.
VBA started in 1991 or 1992 (I don't remember exactly) as an implmentation of VB Version 4 to add functionality to Office Suite. It's a subset of VB language and lacks of certain events that VB handles, among other restrictions.
Basically, if you know VB you can easily switch to VBA and vice versa. With the release of .NET a lot of things changed and you'd probably need to review the whole language structure if you part from a VB or VBA base.
Google "differences between VB and VBA" (and VB and VB.Net) and a lot of articles will be retrieved.
If you have to start from scratch, I guess you have two choices:
a) learn VBA and keep your scope within macros for Office (start by Excel)
b) learn VB.NET and open your scope to the programming world (VBA for Office will come nearly automatically)
Regards!
Briefly VB (Visual Basic) is an independent programming language which reached Version 6 circa 1998, and that has been replaced in 2002 by VB.NET (Visual Basic .NET), which is now by Version 10 of 2010, and Beta 11 of 2011 and sooner will arrive Version 11 of 2012.
VBA started in 1991 or 1992 (I don't remember exactly) as an implmentation of VB Version 4 to add functionality to Office Suite. It's a subset of VB language and lacks of certain events that VB handles, among other restrictions.
Basically, if you know VB you can easily switch to VBA and vice versa. With the release of .NET a lot of things changed and you'd probably need to review the whole language structure if you part from a VB or VBA base.
Google "differences between VB and VBA" (and VB and VB.Net) and a lot of articles will be retrieved.
If you have to start from scratch, I guess you have two choices:
a) learn VBA and keep your scope within macros for Office (start by Excel)
b) learn VB.NET and open your scope to the programming world (VBA for Office will come nearly automatically)
Regards!
vijay.vizzu
Member
Dear SirJB7,
I am impressed with your answer, but can you tell me what is the best way to learn VBA to program in excel. By reading Books or by taking or joining a class. Can you suggest me books which can teach VBA in better and proper programming becoz i want to learn VBA i have little bit knowledge (beginner level) or can u suggest the best way to learn it.
I am impressed with your answer, but can you tell me what is the best way to learn VBA to program in excel. By reading Books or by taking or joining a class. Can you suggest me books which can teach VBA in better and proper programming becoz i want to learn VBA i have little bit knowledge (beginner level) or can u suggest the best way to learn it.
brijendraydv
Member
Hi Vijay,
Its like buck searching for musk in the jungle but musk is itself in his stomach.You can join Chandoo's website to learn and his VBA Classes which is gng on.
Thanks,
Its like buck searching for musk in the jungle but musk is itself in his stomach.You can join Chandoo's website to learn and his VBA Classes which is gng on.
Thanks,
I would add a brief note that exposure to any of these is the most important thing you can add as a learner.
Moving from one to another is not that hard.
VB, VBA and VB.Net all have extra functions that the others don't have,
But the basics of any of them are interchangeable.
I would start with what ever you are going to be able to use most on a day to day basis whilst learning.
Once you understand the basics moving from VB to VBA to VB.Net isn't such a big deal
Moving from one to another is not that hard.
VB, VBA and VB.Net all have extra functions that the others don't have,
But the basics of any of them are interchangeable.
I would start with what ever you are going to be able to use most on a day to day basis whilst learning.
Once you understand the basics moving from VB to VBA to VB.Net isn't such a big deal