E
efandango
I'm a little confused (and out of my depth), but are you saying that the data
will come out via a VBA parser different to what is actually held in the
query/table?. I'm not a seasoned coder and find the arcane synatx of xml
character encoding somewhat baffling. Regarding your suggestion that I should
replace "&" with "& for the KML/XML file, though I can understand that it
will allow for the '&' character to be viewed as '&' within google earth, it
would look odd in the MS Access form/table.
eg:
Cable & Wireless Building
Cable & Wireless Building
So for now, I have to settle for 'Cable and Wireless Building' which is not
an ideal state, but I don't know how to resolve it.
will come out via a VBA parser different to what is actually held in the
query/table?. I'm not a seasoned coder and find the arcane synatx of xml
character encoding somewhat baffling. Regarding your suggestion that I should
replace "&" with "& for the KML/XML file, though I can understand that it
will allow for the '&' character to be viewed as '&' within google earth, it
would look odd in the MS Access form/table.
eg:
Cable & Wireless Building
Cable & Wireless Building
So for now, I have to settle for 'Cable and Wireless Building' which is not
an ideal state, but I don't know how to resolve it.
Brendan Reynolds said:That's a separate issue, the & and < characters have to be escaped because
they have special meaning to the parser. See the section "2.4 Character Data
and Markup" at the following URL ...
http://www.w3.org/TR/REC-xml/
In short, you need to replace "&" with "&" and "<" with "<"
The issue of encoding is described in the same article at section "4.3.3
Character Encoding in Entities"
I know, it's not an easy read, and I can't explain it all. I'm not an expert
on these issues, it's just something I had to muddle through as best I could
for a specific project that I worked on about two years ago. If you think
the code you have now will do what you need, that's great, but make sure to
test it with characters outside the standard ASCII range if there is any
possibility that such characters may ever be included in your real-world
data.
--
Brendan Reynolds
efandango said:Funny you should mention this Brendan, because I have been having problems
with certains characters in the KML file such as these two: ' &. I had to
change the ampersand (&) character to 'and' before google earth would
accept
them. I am not familiar with encoding formats, but assumed the KML was in
UTF-8 encoding format. Here's a link to googles guide on KML where you can
see that they use this type of encoding in their header file.
http://code.google.com/apis/kml/documentation/kml_tut.html
Below is my resultant KML file with adjusted characterss which works fine
in
Google Earth, though it would be much better if it would take the & type
characters:
My KML example:
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.0">
<Document>
<name>Run Points 5</name>
<Folder>
<name>Locations</name>
<open>1</open>
<Placemark><description>Ascot Hotel</description><address>11 Craven Road,
W2, London, UK </address><name>11 Craven Road, W2, London,
UK</name></Placemark>
</Folder>
</Document>
</kml>
Brendan Reynolds said:I'm glad you're making progress. I think you'll find, though, that the
resulting file is not, in fact, in UTF-8 encoding. You may find that this
causes XML parsers to reject the file when it contains characters outside
the standard ASCII range.
I'm not aware of any way to specify the encoding to be used when using
VBA
IO commands. But you can probably avoid problems by changing the
declaration
to match the actual encoding being used, rather than trying to change the
encoding to match the declaration.
On my system, when using the VBA IO commands, the resulting file is in
ISO-8859-1 encoding, so my declaration looks like this ...
Print #intFile, "<?xml version='1.0' encoding ='ISO-8859-1'?>"
I don't know whether VBA always uses this encoding, or whether it may
vary
between OS versions or language versions.
If I remember correctly, I believe I used a utility or sample code that I
found on the 'net to determine the actual encoding that VBA was using.
I'm
afraid, though, that it was some time ago, and I can't remember the
details.
If you really need to specify an encoding other than the one that VBA
uses
by default, I believe you can probably do that using Microsoft's XML
parser,
MSXML.DLL. I haven't actually done this, so I can't provide details, but
if
you want to look into it try searching on 'msxml' at MSDN
(http://msdn.microsoft.com)
--
Brendan Reynolds
Brendan,
That worked.
It seems that while making changes to the code after Douglas's helpful
input, I missed out some of John's essential code snippets. Following
your
suggestion, I went back to John's code, and incorporated them into
Douglas's
latter code suggestions, and it all worked in the end. So a HUGE thank
you
to
John, Douglas and your good self for your help and guidance on this
problem.
For the record, here is the succesful code that will allow the user to
choose a Run Number for a set of addresses and run it out to a Google
Earth
KML file.
Cheers Fellas.
Private Sub Test_Click()
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim rs As DAO.Recordset
Dim strRun_No As String
Dim lngFN As Long
'Create empty text file
lngFN = FreeFile()
Open "W:\Folder\Addresses.kml" For Output As #lngFN
'Output header
'NB: need to double quotes in literal strings
Print #lngFN, "<?xml version=""1.0"" encoding=""UTF-8""?>"
'Print #lngFN, "<?xml version=""1.0"" encoding=""""UTF-8""""?>"
Print #lngFN, "<kml xmlns=""http://earth.google.com/kml/2.0"">"
Print #lngFN, "<Document>"
Print #lngFN, "<name>Address List</name>"
Print #lngFN, "<Folder>"
Print #lngFN, "<name>Locations</name>"
Print #lngFN, "<open>1</open>"
strRun_No = InputBox("Enter the Run No")
If Len(strRun_No) > 0 Then
Set db = CurrentDb()
Set qdf = db.QueryDefs("Generate_KML")
qdf.Parameters("Run No") = strRun_No
qdf![Run No] = strRun_No
Set rs = qdf.OpenRecordset(dbOpenSnapshot)
Do Until rs.EOF = True
Print #lngFN, rs.Fields("KML_Address")
rs.MoveNext
Loop
rs.Close
'Output footer
Print #lngFN, "</Folder>"
Print #lngFN, "</Document>"
Print #lngFN, "</kml>"
Close #lngFN
End If
End Sub
:
The error message is, I believe, complaining about the value of the
variable
'lngFN'. I don't see, in the posted code, where this variable is
declared,
or where a value is assigned to it, or where the file gets opened for
output?
In other words, unless this is a global variable that is declared and
initialized elsewhere, the code seems to be missing something like
this
...
Dim lngFN As Long
lngFN = FreeFile
Open "C:\SomeFolder\SomeFile.txt" For Output As #lngFN
You'll also want to close the file when you've finished writing to it
...
Close #lngFN
--
Brendan Reynolds
Sorry, I forgot to add that this is the line that now highlight
errors
with
''Bad file name or number (runtime error 52)
Print #lngFN, rs.Fields("KML_Address")
:
Douglas
I noticed your 2nd option 'qdf![Run No] = strRun _No'
had a space before the underscore '_No'
but it still comes back with the same error line ('Bad file name or
number
(runtime error 52) as your first option
Here is my Current Code:
Private Sub Test_Click()
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim rs As DAO.Recordset
Dim strRun_No As String
strRun_No = InputBox("Enter the Run No")
If Len(strRun_No) > 0 Then
Set db = CurrentDb()
Set qdf = db.QueryDefs("Generate_KML")
qdf.Parameters("Run No") = strRun_No
qdf![Run No] = strRun_No
Set rs = qdf.OpenRecordset(dbOpenSnapshot)
Do Until rs.EOF = True
Print #lngFN, rs.Fields("KML_Address")
rs.MoveNext
Loop
rs.Close
'Output footer
Print #lngFN, "</Folder>"
Print #lngFN, "</Document>"
Print #lngFN, "</kml>"
'...
Close #lngFN
End If
End Sub
:
Douglas,
this line: qdf.Parameters("Run No") = strRun_No
comes back with 'Bad file name or number (runtime error 52)
your other line 'qdf![Run No] = strRun _No' redlines in the VBA
window
:
Since your parameter doesn't have an underscore in it, try:
qdf.Parameters("Run No") = strRun_No
or
qdf![Run No] = strRun _No
--
Doug Steele, Microsoft Access MVP
(no private e-mails, please)
message
Douglas,
I tried both lines (seperately), but neither worked.
they both throw the following error:
'Item not found in this collection'
I am using 'Run No' as my parameter name without the
underscore
for
the
actual field, [Run_No] with the underscore.
Here is my SQL (with the parameter request)