The information in this article applies to:
SYMPTOMSWhen you add a MAPISession control version 5.0 or a MAPIMessages control version 5.0 to a form and then edit the (Messaging Application Programming Interface) MAPI control properties, a memory corruption error appears. RESOLUTION
One possible resolution is to copy the older Msmapi32.ocx version 1.0.2815
from another computer that is currently running Visual FoxPro version 5.0
or extract the file from the Visual FoxPro 5.0 install disks.
Q135518 HOWTO: Copy Files from Cabinets on DMF-Formatted DisksNOTE: This resolution will only work as long as another application does not install version 5.0 of the Msmapi32.ocx over version 1.0.2815. These applications may include Visual Basic version 5.0, Visual FoxPro for Windows version 5.0a or an executable file created by one of these applications. NOTE: This error has not been corrected in Service Pack 1 or Service Pack 2. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0. MORE INFORMATIONOnce you try to edit or make changes to any of the MAPISession control or MAPIMessages control specific properties, the following error is displayed:
-or- This will not prevent the control from being edited. Click OK and then right-click the control to display the short-cut menu. Choose MAPISession or MAPIMessage Properties to open the Property Pages dialog box. Change one of the properties then click Apply or OK. In Windows 95, the following error message appears: After clicking the Details push button, the following message appears: In Windows NT 4.0, the following error appears: NOTE: If you get this error multiple times, the error log file may get larger. You may delete the User.dmp file to free up the space used by this log file. Steps to Reproduce BehaviorThe following two methods reproduce the application error. Method 1:
Additional query words:
Keywords : kbVFp kbVFp600fix AXSDKControls FxinteropOcx |
Last Reviewed: August 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |