The main problem is probably with your search string. I don't write C#, so you'll have to build the string yourself, but the final result to search for the letter "a" in the subject would be:
"urn:schemas:mailheader:subject" Like '%a%'
Note that the property name needs quotation marks around it.
The easiest way to see the correct syntax, BTW, is to filter a view and then look at the view's SQL tab.

Signature
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
Yeah, that did the trick, great to know what I was overlooking there.
Definitely, thanks for pin-pointing that.
Now I need to return all items, regarless of subject or mail type - calendar
item even.
It may be an emtpy subject field will get me that - but in outlook you must
specify any outlook item when doing an advanced search through the gui.
But if it works, I still don't know what to pass - wild card - to catch
everything. Even still, probably another approach needed to return what I
want anyway.
You know of a webdav clause that would return all items?
The main problem is probably with your search string. I don't write C#, so
you'll have to build the string yourself, but the final result to search for
the letter "a" in the subject would be:
"urn:schemas:mailheader:subject" Like '%a%'
Note that the property name needs quotation marks around it.
The easiest way to see the correct syntax, BTW, is to filter a view and then
look at the view's SQL tab.

Signature
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
> Please advise where this maybe best directed, since I really don't know
> vba
[quoted text clipped - 204 lines]
>
> }
matt - 28 Jul 2007 05:39 GMT
nevermind, this is all I needed
string filter = @"";
Also, imediately below, that was a really cool tip, since I never even
thought to do that before.
> The easiest way to see the correct syntax, BTW, is to filter a view and
> then look at the view's SQL tab.
> Yeah, that did the trick, great to know what I was overlooking there.
> Definitely, thanks for pin-pointing that.
[quoted text clipped - 233 lines]
>>
>> }