.version[enum]

2.401 .version[enum]

This attribute of the document object sets the desired version of the XML toolkit.

When the attribute is changed, the stored DOM tree is deleted and all existing doccursors are invalidated (.mapped = false).

Setting the attribute does not automatically force the XML toolkit to be loaded. When the attribute is queried, it returns the value that it has been set to. The attribute .real_version can be used to check at runtime, whether the desired XML toolkit can be loaded.

The index for this attribute is the toolkit enumeration.

Currently toolkit_windows is the only index value supported, because only Microsoft Windows allows to set the runtime version of the MSXML control. To indicate the version number, the major version has to be multiplied with 100 and the minor version has to be added if applicable. When 0 is given as version number, the system’s default version of the MSXML control is loaded.

Definition

Data type

integer
Access

get, set
changed event

no

Example

MSXML 5.0 shall be used so that the XSD document type is supported.

this.version[toolkit_windows] := 500;

Afterward it is checked if MSXML 5.0 could be loaded.

if (this.real_version[toolkit_windows] = 500) then
  // OK
endif

Note

The versions of the MSXML control differ in the features they support. Only some of the main differences can be listed here. Comprehensive information can be found in the documentation of the MSXML control provided by Microsoft.

MSXML 6.0

Some features that are considered insecure, like DTD’s and embedded schemas, are turned off by default.
Support for XDR Schema is removed.
Support for XML Signatures is removed.

MSXML 5.0 for Microsoft Office applications

Support for XML Signatures.
Support for embedded XSD Schemas.

MSXML 4.0

Support for XML Schemas (XSD).
Support for the Schema Object Model (SOM).
Older versions of the MSXML control are not replaced on installation.
Version-independent ProgID removed.
Legacy code removed:
Non-standard XSL replaced by XSLT 1.0
Non-standard XSLpattern language replaced XPath 1.0.

MSXML 3.0

Compliance with XSLT 1.0 and XPath 1.0 specifications.
Support for namespaces in XPath queries.