E
Egbert Nierop \(MVP for IIS\)
Hi,
The statement above, generates an XML file.
But there are two problems.
First, it does not work on queries. On queries, it does not error, but
produce zero lines of XML.
Second, when I use a table with a primary key (that should be in effect
automatically) the XML-output, is not ordered. That is, it is mostly not
ordered, but sometimes it is.
1) How can that be fixed that below would work?
Application.ExportXML acExportQuery, "qTempSelect", _
path + "qTryGreekToEnglish.xml", , , , acUTF8
(fyi, above works on tables, but produces unordered XML data!)
2) The XLS produces HTML of those, but can XSL order xml data?
( <xsl:for-each select="temp">)
The statement above, generates an XML file.
But there are two problems.
First, it does not work on queries. On queries, it does not error, but
produce zero lines of XML.
Second, when I use a table with a primary key (that should be in effect
automatically) the XML-output, is not ordered. That is, it is mostly not
ordered, but sometimes it is.
1) How can that be fixed that below would work?
Application.ExportXML acExportQuery, "qTempSelect", _
path + "qTryGreekToEnglish.xml", , , , acUTF8
(fyi, above works on tables, but produces unordered XML data!)
2) The XLS produces HTML of those, but can XSL order xml data?
( <xsl:for-each select="temp">)