Pro 96 Import data error (Repairs required)

[ov1]

There is a problem importing data for Zone 2 Ontario Fleenet system

Don S has reviewed the problem, here is his reply.

The DB is sending bad XML...

There is an ampersand in the county text for that system's Site 005. Win96's XML processor (necessarily) aborts when it sees this.

You might want to post a message on RR's "Eastern Canada" forum about this - some database admin is going to have to change the data.

-Don


You can also see the error yourself by entering this URL into Internet Explorer:
http://www.radioreference.com/apps/xml1.1/?sid=2560

The 2560 is the RR DB's "system ID", and is seen in the URL when you navigate to that system through the "normal" DB access:
http://www.radioreference.com/modul...=TRSDB&sid=2560

-Don

 

[blantonl]

This was just fixed... thanks for pointing out.

Lindsay

 

[berrin]

Error Message

Got an error message when trying to import conventional frequencies for a couple of Georgia counties:

XML error detected: no element found

near:


^

while requesting URL:
http://www.radioreference.com/apps/xml/?stid=13

This is a great partnering between you and Don Starr. Thanks for making it all possible!

Bob

 

[blantonl]

Berrin, make sure you have updated the URL to point to xml1.1 not xml

Lindsay

 

[fmon]

Lindsay, I agree with Berrin, you guys are tops.

The Chesapeake VA (independent city) system on your database page has ID numbers different then those listed on Win96 Web Import. IE, Fire/EMS Dispatch is 16016 on your database page but Win96 Web Import list it as 59648. Strangely though, the correct 16016 is imported into the Win96 program. Many other ID's are also listed incorrectly, but import correctly. None of the other systems in my area have this error.

Web Import does import them correctly, so no real complaint other then a surprise when reviewing the data prior to import.

Thanks again for the great work between your guys and the software guys. This addition of conventionals is astonishing.

 

[loumaag]

... Web Import does import them correctly, so no real complaint other then a surprise when reviewing the data prior to import.

Frank,

You should repost this in the Software Support forum. Let Don take a look at it and see. Remember to be specific.

 

[DonS]

The Chesapeake VA (independent city) system on your database page has ID numbers different then those listed on Win96 Web Import. IE, Fire/EMS Dispatch is 16016 on your database page but Win96 Web Import list it as 59648. Strangely though, the correct 16016 is imported into the Win96 program. Many other ID's are also listed incorrectly, but import correctly. None of the other systems in my area have this error.

Web Import does import them correctly, so no real complaint other then a surprise when reviewing the data prior to import.

When I added conventional import to Win96 and Win97, I moved some code around, so that the two apps now share all XML and Web Import modules. I missed a difference between the two ("shifted" vs. "unshifted" IDs). I got it right in the code that actually does the import; the one I missed is only when IDs are placed in the tree in a human-readable form.

I'll be releasing new versions of both apps today (XML file write/read in the import dialog, so you can tweak things like Alpha Tags before actually importing into a P9x file), and will include this fix in Win96.

-Don

 

[loumaag]

...I'll be releasing new versions of both apps today (XML file write/read in the import dialog, so you can tweak things like Alpha Tags before actually importing into a P9x file), and will include this fix in Win96.

Cool! You are a prince!

 

[fmon]

Doggon it Lou, sometimes Don is so on top of things, ya just don't get a chance to do things like this.

You should repost this in the Software Support forum. Let Don take a look at it and see. Remember to be specific

Thank ya Don.

 

[DonS]

Incidentally - they (the changes) are done and posted.

 

[fmon]

Incidentally - they (the changes) are done and posted.

And nicely fixed.