MAPI32.dll problem

[Gavin Steiner]

I hope this is the forum for this question : )

I have a client who's written an application that at the end of the day
sends an email through a call to the MAPI32 DLL, through the profile on the
users desktop. HOWEVER, it's using an old control which needs(?) the Outlook
2000 version of mapi32 dll. If we load Outlook 2003, when the application
attempts to create the email we get the error:

MSMAPI Custom Control
'A MAPI compliant messaging system required
Mapi.dll couldnt be loaded

and then

Can't load custom control DLL 'c:\windows\system32\msmapi.vbx'

The control IS in the directory.

This is preventing my guys from allowing Outlook 2003 to load onto 17 nice
new WS's!

Has anyone seen this, and is there a workaround until we can get onto
developing a more compliant app?

Gavin

 

[neo [mvp outlook]]

It is because the VB control they are using is looking for 16-bit MAPI
support. Outlook 2003 did not ship with these binaries.

 

[Gavin Steiner]

Is there a way around this so that they CAN use Outlook 2003 with the VB
control they have used previously, until they can rewrite their app using
..net?

Thanks,

Gavin

 

[neo [mvp outlook]]

Sure, install Outlook 97 or 98/2000 in Corp/Workgroup mode and then upgrade
to Outlook 2003. This should allow the app to continue working.