OL97: Errors in Outlook Visual Basic Help (Vbaoutl.hlp)

Last reviewed: March 2, 1998
Article ID: Q169751
The information in this article applies to:
  • Microsoft Outlook 97

SUMMARY

This article lists all of the known documentation errors in the Microsoft Outlook Visual Basic Help file (Vbaoutl.hlp), which describes the Outlook object model.

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

Help Topic - Add Method (Recipients Collection) Example

The line of code:

   Set myRecipient.Type = olCC

Should read:

   myRecipient.Type = olCC


Help Topic - Recipients Collection Object

The two lines of code that read:

   Set myRecipient = myItem.Recipients.Add "Jon Grande"

Should read:

   Set myRecipient = myItem.Recipients.Add("Jon Grande")

Help Topic - Recipients Object

This topic has the same problem as "Recipients Collection Object" above.

Help Topic - CreateItemFromTemplate Method Example

The line of code:

   Set myOlApp = CreateObject("Outlook Application")

Should read:

   Set myOlApp = CreateObject("Outlook.Application")

Help Topic - SentOnBehalfOfName Property

The Outlook Visual Basic Help file (Vbaoutl.hlp) incorrectly states that the SentOnBehalfOfName property is read-only.

When you use Microsoft Visual Basic Script with Outlook 97, you should use the SentOnBehalfOfName property to set the "From" field on a form.

For more information on setting a From field, please see the following article(s)in the Microsoft Knowledge Base:

   ARTICLE-ID:  Q168022
   TITLE     :  OL97: How to Set a Form's From Field Using VBScript

Help Topic - NoteItem and ReportItem Objects

The NoteItem and ReportItem objects do not support any events, although the Help file has cross-references that imply they do.

Help Topic - CustomerID Property

This property is read-write, not read-only.

REFERENCES

For more information on installing the Vbaoutl.hlp Help file, please see the following article(s)in the Microsoft Knowledge Base:

   Article-ID:   Q166738
   Title     :   "OL97: How to Install Visual Basic Help"

For more information about creating solutions with Microsoft Outlook 97, please see the following articles in the Microsoft Knowledge Base:

   Article-ID: Q166368
   Title     : OL97: How to Get Help Programming with Outlook

   Article-ID: Q170783
   Title     : OL97: Q&A: Questions about Customizing or
               Programming Outlook


Additional query words: OutSol OutSol97
Keywords : kbprg
Version : 97
Platform : WINDOWS
Issue type : kbdocerr


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 2, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.