Code Portability (MSO 2003)

Topic

New Reply

I’m just now about to order “Microsoft Outlook Programming, Jumpstart for Administrators, Developers, and Power Users”, by Sue Mosher.

Is code (vba, vbscript etc.) potable at all — in other words, as I go through programming Outlook, are the techniques used going to closely approximate those used in Word and Access — maybe even “full apps” done in VB 6?

Regards,
Chuck Billow

Chuck Billow

Reply | Quote

Replies

I never drink code, I prefer beer or wine!

Reply | Quote

Now be nice, Hans… I’m trying to get better at doing my homework…

Chuck

Chuck Billow

Reply | Quote

All Office application use VBA, and the general programming concepts are the same. But each application has its own object model, with objects, properties, methods and events that are specific to that application. Outlook’s object model is highly idiosyncratic, being familiar with the Word, Excel or Access versions of VBA will not help much. Even though I dabble in Outlook programming from time to time, it’s still a foreign language to me.

Tons of examples and links can be found at OutlookCode.Com.

Reply | Quote

Hans:

Yes, OutlookCode.com is where I found the book via a MS bbs… That’s where I found the book. I had figured that since I work more in Outlook, I’d start there…

I’ve taken an initial peek at VB 6, hoping I’d be able to enhance my use of Access… but the focus there is more standalone, and I was more after expanding the tools within Office.

From what you’re saying, it doesn’t seem that it’ll matter whether I start with Outlook or come around to it later, since it’s sort of out there by itself.

Then I’ll be able to come around to Access, Word and Excel…

I had originally started with Access, in trying to understand the sample apps and wizards, and I’ll undoubtedly head there next…

I’m still not totally clear on how VBScript/VBA/VBasic all fit together, except that it seems to just be a set of commands in VBA/VBScript rather than any type of language.

Maybe it’ll come clear as I work through it.

Regards,
Chuck

Chuck Billow

Reply | Quote

[indent]

---

Maybe it’ll come clear as I work through it.

---

[/indent]It’ll all be clear as mud in no time

Reply | Quote

Claude:

Darned if I don’t get THAT feeling a lot!

Chuck

Chuck Billow

Reply | Quote

[indent]

---

I’m still not totally clear on how VBScript/VBA/VBasic all fit together, except that it seems to just be a set of commands in VBA/VBScript rather than any type of language.

---

[/indent] That is precisely what a programming language is, Chuck. When you use VBScript or VBA, which includes the language you use in VB, you are going under the covers of the interface and telling the application (or even the operating system) how to behave. There is not a great deal of portability between application dialects (Word, Excel, Access, Outlook) except at a very granular level because each application has a different set of objects to deal with, so each speaks a somewhat similar but different language, sort of like French, Italian and Spanish.

Reply | Quote

Charlotte:

>>
When you use VBScript or VBA, which includes the language you use in VB, you are going under the covers of the interface and telling the application (or even the operating system) how to behave.
<>
each speaks a somewhat similar but different language, sort of like French, Italian and Spanish
<<

I think I'm looking for the "Latin" of the MS Office country.

Regards,
Chuck Billow

Chuck Billow

Reply | Quote

Chuck,
Why don’t you look into learning “.Net”, as it is going to be the new basis of the “Office” programs. This way you can jump ahead of the crowd, and have a head start. The older code types may be out of use by the time you master them.

DaveA I am so far behind, I think I am First
Genealogy....confusing the dead and annoying the living

Reply | Quote

The “Latin” is the core VBA language. The implementations in Word, Excel, Access, etc., are the French, Spanish, Italian and what have you. Unless you get into managed code with VS.Net (which incidentally isn’t the same as the code you would write *in* Word, Excel, Access, etc.), portability is going to be limited. There is no real rosetta stone because the various implementations aren’t dealing with equivalent objects.

Reply | Quote

Dave/Charlotte:

I have no qualms with “starting” with VB.NET… seeing as how, being, some would say, a somewhat slow study, BUT:

Is it going to REALLY replace VBAsic or VBA? I’ve heard a lot of wailing in the media from current coders, and seconfdly, will it, be any time “soon” (no comments on my learning curve, y’all)?

Chuck

Chuck Billow

Reply | Quote

A few brief thoughts:

• Of the 4 VBA examples you have mentioned, Outlook and Access (in that order) are the most diificult to “easily grasp”
• If you want to get a better grip on the “nuts & bolts” of VBA, using the Record Macro functionality in Excel & Word & then learning how to optimise it is a useful step. There are masses upon masses of posts in the Lounge Archive about optimising code.
• .NET has a very steep learning curve. You’re far better off improving your knowledge of VBA.
• Unless you’ve got a pressing reason, use VBA even if VBScript or VB6 could be alternatives. They will probably become obsolete sooner than VBA will.[/list] HTH

Reply | Quote

Re your last comment, I don’t see scripting becoming obsolete any time soon – with its WMI and ADSI capabilities, it’s just too useful as an admin tool in Windows networks!

Reply | Quote

FTR my comments were targeted specifically for Chuck Billow – based on my understanding of his circumstances. Somehow or other M$ is going to resolve the scripting/security permissions conundrum. This may mean eventually disabling what we now call VBS in many other areas (from what little I’ve seen of Vista), but who knows?

Reply | Quote

unkamunka:

>>
comments were targeted specifically for Chuck Billow
<<

I'm certainly not "the only one", but my uses in this area are almost purely from a personal user standpoint, and not from that of a network admin or any such…

Certainly there is a fair amount of curiosity about how they all work, but I'm looking, as you surmised, more for applicable solutions on a smaller scale than corporate.

Thanks,
Chuck

Chuck Billow

Reply | Quote

Chuck, a belated suggestion about your general question. Many VBA intermediates, once they get a feel for VBA, find the O’Reilly book, VB & VBA in a Nutshell to be an excellent reference. Mine is quite worn out in certain sections, not to mention it has about a hundred post-it flags for sections I needed to learn at some point.

I do not have have any experience with .Net, but there’s also VB.NET Language in a Nutshell; O’Reilly’s Nutshell series generally gets good reviews.

Perhaps references like these will help you improve your skills.

Reply | Quote

John:

Thanks! Off to the store!

Chuck

Chuck Billow

Reply | Quote

unkamunka:

Good points… thanks.

Regards,
Chuck

Chuck Billow

Reply | Quote

[indent]

---

I’m just now about to order “Microsoft Outlook Programming

---

[/indent] Why? I have the book and it is the best book for Outlook, but you would have to be crazy to want to program in Outlook! Plus, the book assumes you actually are a Developer and Power User; ie, that you have a good knowledge of VBA and Outlook.

Reply | Quote

Sam:

You may be right, however, … note my comments to Charlotte.

Thanks,
Chuck

Chuck Billow

Reply | Quote