jonblock
2008-07-22 20:00:10 UTC
A recent update to Outlook seems to have introduced an unexpected error in
displaying the File As field for Contacts created externally (through CDOEX)
in Cached Exchange Mode. The problem occurs in build 11.8206.8202 but not in
build 11.8169.8172. The process for creating these Contacts has been running
for over a year without a problem.
In Cached Exchange Mode, a user's Contacts folder shows blank entries for
the FileAs field for all Contacts synchronized from the external source,
regardless of view mode. Opening the Contact also shows a blank File As
field.
However, switching to non-cached mode, or opening a colleague's Contacts
folder (which isn't cached locally) shows the File As field intact as
expected.
We're using C#, and setting the File As field through contact.FileAs=,
followed by contact.DataSource.Save(). Setting
fields["urn:schemas:contacts:fileas"].Value=, followed by fields.Update(),
doesn't help (they seem to be two paths to the same setting). I can provide
further details of our implementation if necessary.
If there's a canonical way of setting the FileAs field that I've missed, I'd
love to know about it. Otherwise, is this something Microsoft would have to
address in their code for Outlook?
Thanks in advance,
-Jonathan
displaying the File As field for Contacts created externally (through CDOEX)
in Cached Exchange Mode. The problem occurs in build 11.8206.8202 but not in
build 11.8169.8172. The process for creating these Contacts has been running
for over a year without a problem.
In Cached Exchange Mode, a user's Contacts folder shows blank entries for
the FileAs field for all Contacts synchronized from the external source,
regardless of view mode. Opening the Contact also shows a blank File As
field.
However, switching to non-cached mode, or opening a colleague's Contacts
folder (which isn't cached locally) shows the File As field intact as
expected.
We're using C#, and setting the File As field through contact.FileAs=,
followed by contact.DataSource.Save(). Setting
fields["urn:schemas:contacts:fileas"].Value=, followed by fields.Update(),
doesn't help (they seem to be two paths to the same setting). I can provide
further details of our implementation if necessary.
If there's a canonical way of setting the FileAs field that I've missed, I'd
love to know about it. Otherwise, is this something Microsoft would have to
address in their code for Outlook?
Thanks in advance,
-Jonathan