Hi!!I am pretty naive in this area.I need to learn VB.It is better to learn VB6 or VB.net. Any suggestons will be appreciated

Wu,.Net for sure. To the extent that they have implemented OO, it is better to learn this than VB6. You will be a better programmer for it.RegardsTerror

thanks a lot

QuoteOriginally posted by: wuHi!!I am pretty naive in this area.I need to learn VB.It is better to learn VB6 or VB.net. Any suggestons will be appreciatedVB6 will soon leave mainstream support which means it's basically on it's last legs at MS..net is the way forward.

VB.NET is "strategic", so you're stuck with it.However VB6 is closer to Excel VBA, which you may care about.

QuoteOriginally posted by: DCFCVB.NET is "strategic", so you're stuck with it.However VB6 is closer to Excel VBA, which you may care about.Excel in Office 2007 still uses VBA. I wonder when if ever VBA will be removed from Excel. I like VBA and hope the answer is "never".

it depends what do you need it forin general I would definitely suggest learning .NET framework

QuoteExcel in Office 2007 still uses VBA. I wonder when if ever VBA will be removed from Excel. I like VBA and hope the answer is "never".Actually Visual Studio Tools for Office (VSTO) is probably the best way to 'program' Excel these days. It's very powerful stuff, but has a sharp learning curve - however VBA will be around for a long time to come I would imagine.

Hi y'all, I'm new to this forum and programming in general. I'm finding I need to learn some VBA to use in Excel, but I'm thinking I should probably learn some VB6 first. My thinking is if I have an understanding of some basic programming skills that it will give me a better foundation to learn VBA. Does this sound right or do I have it backwards? VBA or VB6 first? Comments please.

QuoteOriginally posted by: untwiggedActually Visual Studio Tools for Office (VSTO) is probably the best way to 'program' Excel these days. It's very powerful stuff, but has a sharp learning curve - however VBA will be around for a long time to come I would imagine.But VSTO can't replace VBA, can it? Personally I was very surprised to see VB.NET missing from Excel 2007.

QuoteOriginally posted by: PanniniBut VSTO can't replace VBA, can it? Personally I was very surprised to see VB.NET missing from Excel 2007.Yup it can indeed. As far as I'm aware pretty much anything you can do in VBA you can do in VSTO. Here's a nice little article

QuoteOriginally posted by: untwiggedQuoteOriginally posted by: PanniniBut VSTO can't replace VBA, can it? Personally I was very surprised to see VB.NET missing from Excel 2007.Yup it can indeed. As far as I'm aware pretty much anything you can do in VBA you can do in VSTO. Here's a nice little articleI did not find the reasons listed there compelling. The article states"2. Object-Oriented Programming Beats Procedural Programming"and "An object-oriented language is, by nature, highly reusable."I don't think blanket statements about the superiority of OOP are justified. Furthermore, VBA does have user-defined types.Making my own generalization, I think some "professional programmers" love OOP because it emphasizes programming methodology and makes what they are doing seem more complicated than it really is.

I too am sceptical about VSTO - which seems like adopting the much more complicated Visual Studio interface just to automate things that you can perfectly well do yourself in ExcelMuch, much better to keep writing VBA user-defined functions and speed them up with Excel DNa (need to adopt .NET math functions and avoid calls to Excel functions)

gelfand,re: "Making my own generalization, I think some "professional programmers" love OOP because it emphasizes programming methodology and makes what they are doing seem more complicated than it really is."I hear you on the above but, now that I have been using languages like VB.Net that lend themselves to OO rather than older clunkier ones, I am finding what everyone says is true. I have been using OO for a while now and it is pretty cool. When IT are enhancing systems, I am just handing them objects from my repository that they can call. They don't need to know what is under the bonnet nor wrestle with maths they don't understand. We just test it to make sure the answers the objects are belching are correct and we are off to the races!I recommend that you go with it and make the investment in understanding OO etc. I think you will find it worth it.Terror

Wow, not a very welcome response. I know I'm new and may be asking newbie type questions, but I didn't think I'd get totally ignored. I was thinking if I had some basic programming skills in VB6 that it would make it easier to learn VBA. Does this sound right or do I have it backwards? VBA or VB6 first? I don't want to put the horse before the carriage (so to speak). So if y'all were totally new to programming (as I am) and had a need to learn and use some VBA in Excel, would you think it's valuable to first get a basic understanding of VB6 as a primer? Any advice would be appreciated.