Page 1 of 2 12 LastLast
Results 1 to 15 of 21
  1. #1
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Code Portability (MSO 2003)

    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
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Code Portability (MSO 2003)

    I never drink code, I prefer beer or wine!

  3. #3
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    Now be nice, Hans... I'm trying to get better at doing my homework...

    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Code Portability (MSO 2003)

    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.

  5. #5
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    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
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  6. #6
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Hornsby Heights, New South Wales, Australia
    Posts
    3,822
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Code Portability (MSO 2003)

    <hr>Maybe it'll come clear as I work through it.<hr>
    It'll all be clear as mud in no time <img src=/S/smile.gif border=0 alt=smile width=15 height=15>
    Cheers, Claude.

  7. #7
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    Claude:

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

    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Code Portability (MSO 2003)

    <hr>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.<hr>
    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. <img src=/S/wink.gif border=0 alt=wink width=15 height=15>
    Charlotte

  9. #9
    Silver Lounger
    Join Date
    Mar 2001
    Location
    Springfield, Ohio, USA
    Posts
    2,136
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Code Portability (MSO 2003)

    <hr>I'm just now about to order "Microsoft Outlook Programming<hr>
    Why? <img src=/S/confused.gif border=0 alt=confused width=15 height=20> 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.
    <font face="Comic Sans MS">Sam Barrett, CACI </font face=comic>
    <small>And the things that you have heard... commit these to faithful men who will be able to teach others also. 2 Timothy 2:2</small>

  10. #10
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    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.
    <<

    This part I've got... I think what I'm after is the best "next step" to getting a better handle on "customizing" the apps... which is, I think, what I spend a great deal of time, and, incidentally, this board's time on. I think it's like: I didn't want to know what the "1"s and "0"'s are (were) for MS-DOS, but rather just how to format, copy, and write batch files to automate my work.

    A good example of where I get, perhaps, distracted (and yet still interested) is when I look at how to set up a file copying batch file that doesn't need a cmd window, but rather works "just like explorer".

    NOT that I'm trying to re-invent the wheel, but rather, by knowing the basics of how it works, I'd have an idea on where to find something else down the road.

    LIKE: If I know how to set up "my own" file copying batch file that operates without a CMD window, then I might very well better understand different processes that I want to use in macros within Office.

    >>
    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
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  11. #11
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    Sam:

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

    Thanks,
    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  12. #12
    Super Moderator
    Join Date
    Dec 2000
    Location
    Renton, Washington, USA
    Posts
    12,560
    Thanks
    0
    Thanked 4 Times in 4 Posts

    Re: Code Portability (MSO 2003)

    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.

    Now running HP Pavilion a6528p, with Win7 64 Bit OS.

  13. #13
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Code Portability (MSO 2003)

    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.
    Charlotte

  14. #14
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Code Portability (MSO 2003)

    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
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  15. #15
    Platinum Lounger
    Join Date
    Nov 2001
    Location
    Vienna, Wien, Austria
    Posts
    5,009
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Code Portability (MSO 2003)

    A few brief thoughts:<UL><LI>Of the 4 VBA examples you have mentioned, Outlook and Access (in that order) are the most diificult to "easily grasp"<LI>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.<LI>.NET has a very steep learning curve. You're far better off improving your knowledge of VBA.<LI>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]<img src=/S/2cents.gif border=0 alt=2cents width=15 height=15> HTH
    Gre

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •