locked Re: : HRD DEFECT - HRD TCP Logging Failure


Jim - N4ST
 

HRD is obviously doing some pseudo data-check clean-up when a manual update is performed on a QSO.
It is deleting both the DXCC code and the Country Name that were in the database before the manual update was performed.
HRD needs to address this.
Still, it is weird that the vast majority of countries are recorded correctly and survive a manual update of the HRD Logbook if the .18 test version JT-Alert is used.
Was the .18 version not actually using the TCP logging interface?

__________
73,
Jim - N4ST

From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Monday, November 2, 2015 05:09
To: HamApps@yahoogroups.com.au
Subject: Re: [HamApps] Re:: HRD DEFECT - HRD TCP Logging Failure


On 2/11/2015 8:35 PM, 'Chas Cartmel' chas@cartmel.me.uk [HamApps] wrote:
As for losing the data, if it is not sourced externally then the option must be internally.
Tnx Chas,
That's it exactly. HRDLogbook is providing the Country Name (as it displays it in its main listview) derived from the JTAlert supplied DXCC. HRDLogbook is then removing that Country Name when it modifies its own log entry (no JTAlert involvement). Bottom Line... this is a HRD Defect or by design.

de Laurie VK3AMA


________________________________________
Posted by: "Laurie, VK3AMA" <vk3ama.ham.apps@gmail.com>
________________________________________

Join Support@HamApps.groups.io to automatically receive all group messages.