We have developed a messageStore add in which uses extended Mapi and
exchange client extensions.

We are presently porting the client to work correctly with the new OL2007
features, one of which is the new desktop search query builder.

I have an issue if I build a search with the importance field set to normal
I get what i expect that is a IMAPIFolder::SetSearchCriteria on
PR_IMPORTANCE, value set to 0, which is normal.
But if I can this value to be either HIGH, or LOW then instead I get content
restrictions on the to, bcc, cc and from fields all with the content of the
string value 'HIGH' or 'LOW' respectively. This is totally unexpected, I
would have expected it to have done the same as above as the normal search
except with values 1 or -1 for low.

Is this a bug, as if I issue a search through advanced find on a folder then
I get the expected SRestriction.

Got the answer - it was a bug in beta2 and is now fixed and working as
expected in beta2 TR.

Hope it stays fixed for the released version - p


"T-rev" wrote in message
...
We have developed a messageStore add in which uses extended Mapi and
exchange client extensions.

We are presently porting the client to work correctly with the new OL2007
features, one of which is the new desktop search query builder.

I have an issue if I build a search with the importance field set to
normal I get what i expect that is a IMAPIFolder::SetSearchCriteria on
PR_IMPORTANCE, value set to 0, which is normal.
But if I can this value to be either HIGH, or LOW then instead I get
content restrictions on the to, bcc, cc and from fields all with the
content of the string value 'HIGH' or 'LOW' respectively. This is totally
unexpected, I would have expected it to have done the same as above as the
normal search except with values 1 or -1 for low.

Is this a bug, as if I issue a search through advanced find on a folder
then I get the expected SRestriction.