Microsoft KB Archive/166549: Difference between revisions
(importing KB archive) |
m (Text replacement - "&" to "&") |
||
| (One intermediate revision by the same user not shown) | |||
| Line 65: | Line 65: | ||
== MORE INFORMATION == | == MORE INFORMATION == | ||
Microsoft has planned the following added feature for inclusion in Microsoft Exchange version 5.0 U.S. Service Pack 1. Hexadecimal numbers as well as strings will be allowed, so you can refer to a named property by a GUID and | Microsoft has planned the following added feature for inclusion in Microsoft Exchange version 5.0 U.S. Service Pack 1. Hexadecimal numbers as well as strings will be allowed, so you can refer to a named property by a GUID and "0x1234." Tthe hexadecimal number must start with "0x," followed by four hexadecimal digits, for example "0x0012."<br /> | ||
<br /> | <br /> | ||
The following is an example of using strings or a hexadecimal number: | The following is an example of using strings or a hexadecimal number: | ||
<pre class="fixed_text"> Fields.SetNameSpace( | <pre class="fixed_text"> Fields.SetNameSpace("0006200300000000C000000000000046") | ||
Fields.Item(& | Fields.Item(&H81010000) | ||
</pre> | </pre> | ||
NOTE: Any string starting with | NOTE: Any string starting with "0x" will be treated the same as a hexadecimal number. "NNNNNNNN" will not be converted to a hexadecimal number. Hexadecimal entries will only be accepted up to eight hex digits.<br /> | ||
Latest revision as of 12:29, 21 July 2020
Article ID: 166549
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Client 5.0
- Microsoft Exchange Client 5.0
This article was previously published under Q166549
SYMPTOMS
The SetNamespace command only works for accessing named properties by name and not by proptag. Named properties can be referred to a by a GUID and a name (a string) but not by a GUID and a hexadecimal number such as 0x1234.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
Microsoft has planned the following added feature for inclusion in Microsoft Exchange version 5.0 U.S. Service Pack 1. Hexadecimal numbers as well as strings will be allowed, so you can refer to a named property by a GUID and "0x1234." Tthe hexadecimal number must start with "0x," followed by four hexadecimal digits, for example "0x0012."
The following is an example of using strings or a hexadecimal number:
Fields.SetNameSpace("0006200300000000C000000000000046")
Fields.Item(&H81010000)
NOTE: Any string starting with "0x" will be treated the same as a hexadecimal number. "NNNNNNNN" will not be converted to a hexadecimal number. Hexadecimal entries will only be accepted up to eight hex digits.
Keywords: kbusage KB166549
