On my current working computer, XP and Access 2002 / XP are running. References offered in the menu as to MSXML range from v2 to v6, which is probably normal on XP. I am to use MSXML late binding, i.e.
Code:
Dim domXXX As Object
Set domXXX = CreateObject...
I implemented this successfully on my current machine:
Code:
CreateObject("MSXML.DOMDocument")
works fine. But I know that on computers running Vista or Win7 there is only a msxml6.dll. I will not ship such system libraries together with our product (for an installation on every workstation, ha ...). If I import msxml v6 temporarily during development, the root object is no longer namend MSXML, but MSXML2. Does that mean, that
Code:
CreateObject("MSXML.DOMDocument")
will generate an error under Vista or Win7? Or will MSXML6 interpret the old object declarations? If not, which is the "most proper" way to react? Query the registry, if MSXMLv2 is there and registered, then
Code:
if ... then strDOMType = "MSXML.DOMDocument" else strDOMType = "MSXML.DOMDocument"
CreateObject(strDOMType)
? If so, which registry keys would be interesting? Is there another way to query valid, import-ready libraries? Or should I, easier, define strDomType dependent on the Windows version?
