OL97: How to Programmatically Resolve a Contact's E-mail Address

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

SYMPTOMS

In Microsoft Outlook 97, if you programmatically set a Contact's e-mail address, the e-mail address is not checked (or "resolved") against an Address Book. Therefore, the Contact's e-mail address is not added to the Outlook Address Book.

CAUSE

This is a limitation of Outlook 97.

RESOLUTION

NOTE: This problem was fixed in Outlook 98. Outlook 98 will resolve the e-mail address when the item is saved.

You can use the CommandBars object model to execute the Check Names menu command and resolve the e-mail address. However, this workaround requires that you display the Contact window.

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

This example code is designed to run from another Microsoft Office 97 program using Visual Basic for Applications, or from a separate Visual Basic (VB) application. In order to use this code you must reference the "Microsoft Outlook 8.0 Object Library" from within the editor. Consult your editor's documentation for how to reference available object libraries.

The following Outlook automation code is an example of how to workaround this issue:

   Sub ResolveContactAddressViaCheckNames()
      Dim ol As Outlook.Application
      Dim olns As NameSpace
      Dim myContact As Object
      Dim Menu as Object
      Dim Command As Object
      Set ol = New Outlook.Application
      Set olns = ol.GetNamespace("MAPI")
      ' Create a new Contact item
      Set myContact = olns.GetDefaultFolder(olFolderContacts).Items.Add
      With myContact
         ' Set the relevant fields for the contact
         .FullName = "John Smith"
         .Email1Address = "jsmith@msn.com"
         .Email1AddressType = "SMTP"
         ' Display the contact (required)
         .Display
      End With
      ' Set the Tools menu on the item's menu bar
      Set Menu = ol.ActiveInspector.CommandBars("Tools")
      ' Sets the command on the menu
      Set Command = Menu.Controls("Check Names")
      ' Actually executes the Check Names command
      Command.Execute
   End Sub

REFERENCES

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 : kbcode kbprg
Version : 97
Platform : WINDOWS
Issue type : kbhowto


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 17, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.