Is this CDO version likely to have any adverse affects on ASP/CDO server
Looking for a good book on ADSI, Outlook 2000 and Exchange 2000 development?
If so, check out:
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. ? 2002 Microsoft Corporation. All rights
> Is this CDO version likely to have any adverse affects on ASP/CDO server
Hi Tom, thanks for the reply.Quote:> Yes if you try to do things that try to prompt for user acceptance such as
> sending mail, accessing address properties, etc.
How about something as simple as:
x = objMessage.Sender
Do you mean that accessing an address like this would be a problem?
I used to do the following for my CDO client application
1)Impersonate user using winapi calls LogonUser and ImpersonaleLoggonOnUser
2) Create a dynamic profile based on user's credentails
3) Log on to user's exchange server and do some work
The above code used to work fine with CDO 1.21 distributed with Outlook 98
and Outlook 2000
However when I tried the same with CDO 1.21s distributed by Outlook XP/2002
I cant even get to Logon to the user's exchange server
I get MAPI_E_LOGON_FAILED or MAPI_E_FAILOVERONPROVIDER
Does that mean with cdo 1.21s impersonating a user and then accessing
exchange is not allowed.
If anybody has been able to impersonate an user and use cdo pls let me know.