FIX: MAPI: Calling ResolveName Method Results in GP Fault

Last reviewed: October 29, 1997
Article ID: Q147571

The information in this article applies to:

Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0

SYMPTOMS

A general protection (GP) fault occurs when the ResolveName method of a Message Control object is called.

CAUSE

The RecipDisplayName property of the Message Control object is null.

WORKAROUND

Before calling the ResolveName method, make sure you have populated the RecipDisplayName property with a non-null value.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been fixed in Visual FoxPro 5.0a.

MORE INFORMATION

Steps to Reproduce Problem

Create a new form, and place MAPI Message and Session controls on it. Name the controls OLEMessageCtrl and OLESessionCtrl respectively.
Place a command button on the form, and place the following code in the command button's Click event:
ThisForm.OLESessionCtrl.SignOn
WITH ThisForm.OleMessageCtrl
```
     .SessionID = ThisForm.OleSessionCtrl.SessionID
     .Compose
     .RecipAddress = "xxx"
     .ResolveName
     .Send(1)
```
ENDWITH

Keywords          : buglist3.00 buglist3.00b buglist5.00 FxinteropOcx vfoxwin vfpfix5.0a kbinterop kbbuglist kbfixlist
Technology        : kbole
Version           : 3.0 3.0b 5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

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