Q185385 - BUG: MSMail Command Extensions Do Not Work in Outlook 98

PSS ID Number: Q185385

Article Last Modified on 10-21-2000

The information in this article applies to:

Microsoft Exchange Development Kit (EDK) 5.0, 5.5

Symptoms

MSMail command extensions work in the Outlook 97 and Exchange 4.0 and 5.0 clients but not in Outlook 98. When a customer upgrades to Outlook 98, applications depending on a MSMail command extension stop working and no error is displayed.

Cause

MSMail command extensions do not work in Outlook 98.

Resolution

A temporary work around is to create a C++ Outlook client extension to place the functionality in the client.

Status

Microsoft has confirmed this to be a bug in Microsoft Outlook 98. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

More Information

Steps to Reproduce Behavior

Create a Visual Basic (VB) application that displays a form.

Create an EXE file named Project1.exe and save it on the root of the C drive.

Create a text file named Msmail.ini or Msmail32.ini with the following code:

      [Custom Commands]
      Foot=3.0;;;;appxec32.dll;c:\project1.exe;1000000000000000

Save the text file in the \Windows or \Winnt directory (which ever applies).

Make sure Appxec32.dll is located in the \Windows\system or \Winnt\system32 directory (whichever applies).

Start Outlook on the computer and you will see the following:
- On a PC with Outlook 97 the VB program executes.
- On a PC with Outlook 98 the VB program will not execute.

Additional query words: EDKAPI ExchExt

Keywords:
Issue Type: kbbug
Technology: kbEDKsearch kbAudDeveloper kbExchangeSearch kbEDK500 kbEDK550