Hi,
I am trying to create a task in Outlook. I used the a similair metod like in CU397, "NewMessage", but using OTask object instead of OSendMail.
.....
OTask.Subject := Subject;
OTask.DueDate := WORKDATE;
OTask.Body := Body;
TaskSaved := OTask.Save;
the save metod generates an error:
"There is no IMessage object assigned to this Item"
Any trials to create, assign etc. to OTask object was without any success.
Is there a "Developer guide", Help or any description how to use the OHandler.dll?
0
Comments
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
But...the initial idea was to send an assigned task. With tihs metod there are two "security" dialog windows opened from outlook:
"a porgram is trying to access e-mail.....blah blah"
and when sending the task:
"a program is trying to automaticlaly send e-mail...."
The user have to click both. Therefore I prefer the OHandler, where the extended MAPI is wrapped and will work without those inconvient dialogs....
Any other ideas?
I know there is something like "clickyes.exe":
http://www.google.be/search?hl=nl&q=clickyes.exe&meta=
May be this can be helpful?
Further, there are some registry hacks you can apply to avoid these messages, but you'll have to google some more...
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
if the salesperson has filled the OL synchornization fields, this code creates a task, without any warnings. But the OLTask object does not know the "Assign" metod and "Recipients" property :-(
Waldo: your solution win !
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
I found a nice and free utility:
http://www.mapilab.com/outlook/security/
"Advanced Security for Outlook" solves the security windows. In first attempt it catches the "violator", the user can manulaly and permanently allow or deny access and by the next call, there are no annoying windows :-)
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog