We're using MSXML5 in a project (References | "Microsoft XML, v5.0").
The project will be distributed very widely to many of our
organization's vendors.

I understand that Excel 2003 only includes XML if you buy the
Professional version of Office, or the standalone version of Excel;
XML is not included if you get Excel from the Standard Edition of
Office 2003.

Does that restriction include the MSXML5 library?

If so, what if affected users -- those who are still on Excel 2003,
and got it through Office Standard 2003 -- download and install MSXML6
from Web Services Extensions? Will our code's reference to MSXML5 work
for them? Or will they have to get MSXML5, which is not available as a
separate download?


Thanks,

Greg

I just noticed that the declaration look like this:

Public HttpReq As MSXML2.XMLHTTP30

(I inherited the XML part of this project; someone else wrote it all.)

Does that mean we're really using MSXML2 (from the MSXML5 library),
not MSXML5? If so, what about using late binding, so that it doesn't
matter whether the installed XML library is v5 or v6?

Thanks for any suggestions.

Greg


On Feb 21, 11:50 am, Greg Lovern wrote:
We're using MSXML5 in a project (References | "Microsoft XML, v5.0").
The project will be distributed very widely to many of our
organization's vendors.

I understand that Excel 2003 only includes XML if you buy the
Professional version of Office, or the standalone version of Excel;
XML is not included if you get Excel from the Standard Edition of
Office 2003.

Does that restriction include the MSXML5 library?

If so, what if affected users -- those who are still on Excel 2003,
and got it through Office Standard 2003 -- download and install MSXML6
from Web Services Extensions? Will our code's reference to MSXML5 work
for them? Or will they have to get MSXML5, which is not available as a
separate download?

Thanks,

Greg