p2p.wrox.com Forums

p2p.wrox.com Forums (http://p2p.wrox.com/index.php)
-   Beginning VB 6 (http://p2p.wrox.com/forumdisplay.php?f=75)
-   -   VBA vs Visual Studio for Office (http://p2p.wrox.com/showthread.php?t=63853)

lovNexcel November 17th, 2007 11:52 PM

VBA vs Visual Studio for Office
Hi all,
First, my apologies if this is not the right forum..

I just recently got laid off and I'm using some my time to learn how to create macros (for the first time) in Excel and Powerpoint in order to the use the programs more efficiently.

I am SOOOO confused as to what the scoop is with VBA vs. VB net vs Visual Studios? Is there an expert that can provide me with some guidance given that:
--> I am new to programming and only intend to learn code in order to create macros in Excel & Powerpoint

Here are my questions:
1) Which programming language should I invest my time to learn if you were in my situation?
2) Will this programming language be compatible to program macros in older / newer versions of excel / powerpoint?
3) If I create a macro in (for eg.) excel 2007, will it run in excel 2003?

Thanks so much for your help!!!!!

Excel rocks!

BrianWren November 19th, 2007 12:32 PM

VBA is VB 6 is VBA. VB 6 is an implementation of VBA that allows you to create stand-alone programs with it, where as VBA on its own requires a host, (such as Word, Access, AutoCAD, etc.).

VB.NET is a major re-writing of VB. The changes are vast, even down to the general approches to everything.

The question is really not answerable. There are places that need full-time programmers to handle their implementations of Office products. There are places that need full-time programmers to handle their implementations of AutoCAD. But there are places that only hire .NET programmers. Yo uneed to figure out what you want to do, find out how the shops that do that are configured, and target that configuration.

Any programming you learn will be a case of learning good programming habits, or bad programming habits. If you do the former, you will have a much easier time adapting to some shhop or others needs.

I think the answer for # 3 is no. But you should be able to past the code out of the editor window into the editor window of the older version, and focus on correcting the syntax errors that are generated that way.

Excel is pretty good for what it is good for, but remember that it is not a relational database. (In fact, for the most part, it is not a database at all.)

All times are GMT -4. The time now is 10:22 AM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.