Re: Accesing reminder minutes as Integer

Why are you using GetNamesFromIDs? You (or easyMAPI) need to call
GetIDsFromNames, assume no property type is set (i.e. you get 0x81E90000),
and explicitly "or" the returned value with the appropriate type (PT_LONG).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"RAPWare" <RAPWare@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4517E856-F96D-4E9C-A10F-2986A05A5CDC@xxxxxxxxxxxxxxxx
Why did it change the type from PT_BOOLEAN to PT_LONG?

The questions are:
1) Why would the "GetNamesFromIDs" return 81E9000B instead of 81E90003
2) Why does SetProps raises an error when trying to set 81E90003
3) Why does the happen on only 1 system (after installing some updates).
The
same code runs on several hundreds of other systems without problems.

Do you have EasyMapi source code to step through?

Yes, but I can't simulate the problem and neither can Chris anymore.

After looking back through my mail conversation with Chris I did found
something that wasn't mentioned in this thread.

I had Chris save a message as a .msg file so I could examine it. When I
looked at it the 0x8501 property it was listed several times in the list
of
properties. It was however listed as PT_LONG.

My guess is that somehow several messages in his clients messagestore got
corrupted, possibly by one of the updates they installed.

Peter.

"Dmitry Streblechenko" wrote:

Why did it change the type from PT_BOOLEAN to PT_LONG? Sounds like a bug
to
me...
Do you have EasyMapi source code to step through?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"RAPWare" <RAPWare@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:52A9C0F2-F9C0-4C70-AEFB-B9031F767544@xxxxxxxxxxxxxxxx
Hi Dmitry,

The following was the case:
1) One of the properties returned by "GetNamesFromIDs" was 81E9000B.
2) Easy MAPI transformed this into 81E90003 (it assumes that this
particular
named property must be a PT_LONG)
3) After setting a property value for 81E90003 a MAPI exception was
raised.

It was not the reading of the property that raised the exception it was
the
setting of a property value that raised the exception. The MAPI
exception
indicated that the MAPI subsystem actually expected a value for
81E9000B.

Very strange.....



"Dmitry Streblechenko" wrote:

Not exactly reassuring :-)
Did you try to step through the EasyMAPI code that sets the property
type
specified as the parameter (PT_LONG) to make sure it always does that?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

<chrisa@xxxxxxxxxxxxxxx> wrote in message
news:1169128285.033958.276440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You're gonna love this. Or more likely hate this...

It's fixed itself. I tested our app on their server before trying a
new
version with some changes installed, and it went through fine.

Maybe the server got a nice christmas present and felt like being
nice.
Or something. I don't know.

Many thanks for all your help, sorry it turned out to be a pile of
poo...

Chris.









.

Relevant Pages
Quantcast