E
Eric
...or is it limited like the Outlook Object Module (OOM)?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
H
Hollis D. Paul
In addition to OOM, you can use CDO--but what, specifically, are youEric said:...or is it limited like the Outlook Object Module (OOM)?
trying to access? And what version of Outlook are you using?
Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
Mukilteo, WA USA
E
Eric
PR_MESSAGE_FLAGS, trying to clear the "unsent" flag. Using Outlook
2000.
The main reason I want to clear the unsent flag is because Pocket
Outlook for the Pocket PC 2002 now wants to handle those "unsent"
messages differently than others, and I want the messages I dump in
the inbox to work just like an email which was downloaded from a mail
server. I can do this with MAPI, but MAPI has to many tech. support
issues, unlike OOM which always seems to work (if Outlook works, OOM
usually works, but MAPI is another story).
2000.
The main reason I want to clear the unsent flag is because Pocket
Outlook for the Pocket PC 2002 now wants to handle those "unsent"
messages differently than others, and I want the messages I dump in
the inbox to work just like an email which was downloaded from a mail
server. I can do this with MAPI, but MAPI has to many tech. support
issues, unlike OOM which always seems to work (if Outlook works, OOM
usually works, but MAPI is another story).
E
Eric
I did figure out that I could clear the "unsent" flag using simple
MAPI, with MAPISaveMail(), then turn around and use the OOM to set the
rest of the fields. I might end up going this route if I find out
that simple MAPI isn't as buggy as extended MAPI. Since even simple
MAPI can set this MAPI property it almost seems like a bug that the
OOM doesn't give you write access to "Sent" or "Submitted" properties
until the item is saved for the first time.
One weird thing, which might be beyond this newsgroup, is that after I
save the message with MAPISaveMail(), then open with OOM and modify
the "MessageClass" field, the icon for the message shows up as the
icon for the new class, but when I open it it still uses the standard
email form instead of the custom form I have setup for that message
class. However, when I add a new message using just OOM, and no
MAPISaveMail() calls, it uses the correct custom form. Anyone ever
had this problem?
MAPI, with MAPISaveMail(), then turn around and use the OOM to set the
rest of the fields. I might end up going this route if I find out
that simple MAPI isn't as buggy as extended MAPI. Since even simple
MAPI can set this MAPI property it almost seems like a bug that the
OOM doesn't give you write access to "Sent" or "Submitted" properties
until the item is saved for the first time.
One weird thing, which might be beyond this newsgroup, is that after I
save the message with MAPISaveMail(), then open with OOM and modify
the "MessageClass" field, the icon for the message shows up as the
icon for the new class, but when I open it it still uses the standard
email form instead of the custom form I have setup for that message
class. However, when I add a new message using just OOM, and no
MAPISaveMail() calls, it uses the correct custom form. Anyone ever
had this problem?
H
Hollis D. Paul
I would opine that you are one-offing the form when you do those mapiEric said:One weird thing, which might be beyond this newsgroup, is that after I
save the message with MAPISaveMail(), then open with OOM and modify
the "MessageClass" field, the icon for the message shows up as the
icon for the new class, but when I open it it still uses the standard
email form instead of the custom form I have setup for that message
class. However, when I add a new message using just OOM, and no
MAPISaveMail() calls, it uses the correct custom form. Anyone ever
had this problem?
calls, and that is why it is not using your custom form. Check the size
value to see if it has jumped by about 15Kb. If so, then you really do
not want to do that.
The only comment from the experts so far has been that the
PR_MESSAGE_FLAGS property is read-only in OOM. You might want to check
its status in CDO, which you can usually run in a concurrent session
with OOM, but I have little experience with it.
Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
Mukilteo, WA USA