|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
January 28th 07, 12:19 AM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
MAPI32.dll problem
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 
|
| Ads |
|
#2
January 28th 07, 01:03 AM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
MAPI32.dll problem
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" wrote in message ... 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
|
|
#3
January 28th 07, 02:16 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
MAPI32.dll problem
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]" wrote in message ... 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" wrote in message ... 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
|
|
#4
January 28th 07, 03:22 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
MAPI32.dll problem
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. "Gavin Steiner" wrote in message ... 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]" wrote in message ... 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" wrote in message ... 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
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| MAPI32.dll problems | JimB | Outlook - Installation | 16 | December 28th 06 08:37 PM |
| fixmapi32.exe does not fix problem of corrupt mapi32.dll | philrharris | Outlook - Installation | 4 | November 14th 06 05:25 PM |
| Getting MAPI32.DLL is corrupt... | tlc_13200@hotmail.com | Outlook - Installation | 2 | September 21st 06 05:10 PM |
| MAPI32.DLL error message | HarryL | Outlook - Installation | 4 | June 22nd 06 08:23 PM |
| MAPI32.DLL | JT | Outlook - Installation | 3 | June 20th 06 03:19 AM |
Linear Mode
