To any user who ran my last version 2.20 of my DBChecker -- AND -- you
had the "Correct LAT/LON" button become active - because there were
+/- sign errors found -- pse revert (if you made a backup of your Refdata)
to your previous copy of the refdata.mdb file ...
If you DID NOT save a copy (before running my program) -- PSE, send me your
"current" Refdata.mdb file -- and I will correct it here ---
I am the one who made the coding mistake -- so, I will assist directly ---
What happened - and I am right now looking at it -- was the Corrections WERE
MADE ALL OK in the Prefix-Pri table -- but, in the Alias-MAP and CALL-MAP
tables,
you ended up with "just" a + sign in the Lat/Lon columns (of the entries that
were trying to be corrected) ...
I "will" post an updated version -- once I have tested to make sure that the
Alias-Map and Call-Map LAT/LON updates were made properly ...
NOTHING is lost -- because, if you did not save a backup copy of your
Refdata.mdb
file --- you CAN (and pse do) (zip up your Refdata.mdb file and SEND it to me)
--
I will return it corrected.
Sorry guys!!!!!
73 Joe wa6axe
______________________________________________________________
Dxbase mailing list
Home: http://mailman.qth.net/mailman/listinfo/dxbase
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
