OK, but it did change the county - I originally entered Apache county and it changed it to Yavapai (which is the correct county). It just didn’t change the grid square.
— Darrell > On Jan 7, 2018, at 9:20 AM, Jim Reisert AD1C <jjreis...@alum.mit.edu> wrote: > > On Sat, Jan 6, 2018 at 11:57 AM, Darrell Earnshaw NR3Y wrote: > >> Thanks to SV1DPI and WD4LBR, I‘ve just got my QRZ XML settings fixed. >> However, when I try to update an existing QSO, the Grid Square is not >> updated. >> >> Steps: >> >> Enter a bogus QSO, filling in a wrong county and fictitious grid square >> Select that QSO and do the F-3 magic to invoke QRZ XML lookup >> Update QSO with new information >> County is updated correctly >> Name is inserted correctly (it was blank previously) >> Gird is NOT updated - the fictitious grid square remains >> >> I’m assuming this is not by design? > > My understanding is that clicking on the Update button in the F3 > window will not replace any field in the QSO that is already > populated. DX4WIN assumes that whatever the user put there is more > correct than the external data source. For example, if the F3 windows > gives CO, Adams as the state/county, and the QSO has the state set to > MN, neither the state nor county will be changed in the logbook. > > -- > Jim Reisert AD1C, <jjreis...@alum.mit.edu>, http://www.ad1c.us ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
