OL97: How to Use Variables with Find and Restrict Filters

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

SUMMARY

This article illustrates how to use a Visual Basic Scripting Edition (VBScript) variable as part of the filter string for the Find or Restrict methods in the Microsoft 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

The Find method can be used to return a single Outlook item that matches certain criteria. The Restrict method returns a subset of a collection of items that matches certain criteria. The criteria for both methods is specified in the same way, as illustrated in the example below.

The Vbaoutl.hlp Help file that documents the Outlook object model incorrectly states that you cannot use a variable as part of the filter for these two methods. The following VBScript code sample illustrates syntax that uses variables as part of the filter.

   ' Set the MyFldr object to the default Inbox.
   Set MyFldr = Item.Application.GetNameSpace("MAPI").GetDefaultFolder(6)

   ' MyVar is the subject of the mail message to search for.
   ' Change this to match a mail message in your Inbox.
   MyVar = "Please read!"

   ' This is the standard approach without using a variable.
   Set Itm = MyFldr.Items.Find("[Subject] = ""Please read!""")

   ' This approach uses Chr(34) to represent a quotation mark.
   Set Itm = MyFldr.Items.Find("[Subject] = " & Chr(34) & MyVar & Chr(34))

   ' This approach uses double quotation marks to represent a
   ' quotation mark.
   Set Itm = MyFldr.Items.Find("[Subject] = """ & MyVar & """")

   ' Display the date/time the found mail message was created (just
   ' for verification purposes).
   MsgBox Itm.CreationTime

REFERENCES

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

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

For more information on known error messages in Vbaoutl.hlp, please see the following article in the Microsoft Knowledge Base:

   Article-ID:   Q169751
   Title     :   OL97: Errors in Outlook Visual Basic Help (Vbaoutl.hlp)

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