Microsoft KB Archive/251549

= XWEB: Using Exchange Schema Properties in Web Forms for HTML Name Attributes Produces Non-scriptable Forms =

Article ID: 251549

Article Last Modified on 2/26/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q251549





SYMPTOMS
When you use the standard Exchange 2000 Server schema properties when you write scripts for forms, the forms may not work across version 3.x Web browsers, including Microsoft Internet Explorer and Netscape Navigator. For example, forms scripted to do validation or forms scripted for dynamic values may not work.



CAUSE
This behavior can occur because the current syntax that is used to define forms in the Morpheus forms renderer requires that form fields have a name attribute equal to the schema property name.

Standard Exchange 2000 schema properties contain the colon, which differs from the common syntax that defines forms.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.



MORE INFORMATION
In Internet Explorer 3.0 or later and Netscape Navigator 3.0 or later, the backward-compatible cross-browser syntax for accessing form elements is

document.FormName.FieldName.value

This syntax may not work when an Exchange 2000 schema is used for FieldName.

NOTE: Internet Explorer 4.0 and later provides the following alternative format:

document.forms('theForm').item('urn:schemas:contacts:givenName').value

However, this format is not supported in Netscape Navigator.

Keywords: kbbug kbnofix KB251549

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.