View Single Post
  #4  
Old October 23rd 09, 08:45 AM posted to microsoft.public.outlook.program_addins
Mark McGinty
external usenet poster
 
Posts: 25
Default Restrict throwing 'Condition is not valid' error


"Sue Mosher [MVP]" wrote in message
...
Is there a possibility that this machine is set to use Outlook in a
language
other than English?


Hi Sue,

Did I ever send you a WTG note about your book? (You may recall helping me
a couple of years ago, and I bought a copy of your book to keep a clear
conscience.) If not, nicely done, concise yet sufficiently detailed; a
useful reference without a doubt! (My intentions are always golden when I
decide to send such notes; follow-through could use some work.) :-)

Anyways, I can't say no possibility but I think it unlikely, the PC is in
the US, in email replies from this box, the header that describes the
original email are generated in English, date format is US... make that
highly unlikely.

But for argument's sake, what if it is? OOM property names aren't
language-specific, right?


Thanks,
Mark



Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54



"Mark McGinty" wrote:

Greets,

Out of the thousands of installed copies of our AddIn, exactly one throws
an
error when we call Restrict aginsts the items collection of the default
contacts folder. The filter expression is static, and is as folllows:

[MessageClass] 'IPM.DistList'

Since it works as expected on every other machine, I can't imagine how
this
might be a problem in my code, because I can't imagine how this condition
would be invalid in any folder.

The system is Outlook 2003, connected to Exchange, using CEM. I asked
the
user to perform an advanced search using the same criteria on this
machine,
he said it returned the items he expected.

The user logged-into Exchange from another machine, and our AddIn ran
against his contacts without errors. The user said he forced the .OST to
be
regenerated on the problem machine, he said it didn't change the problem.

Anyone ever seen this, or have an idea what might cause it? I'm thinking
Outlook might need to be reinstalled, but I don't want to suggest that
frivolously.


TIA,
Mark


.



Ads