locked Re: JTAlert cannot log to a HRD Access logbook unless it is open

WU9D <mike@...>

Thank you for clarifying Laurie. I was running HRD in conjunction with WSJT-X and JTAlert before, so the logbook was open. No problem, all I must do is run the logbook on its own. It complains about not having the HRD server running but I can ignore that.



Mike WU9D


From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA) via groups.io
Sent: Saturday, April 24, 2021 1:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert cannot log to a HRD Access logbook unless it is open


On 25/04/2021 1:58 am, WU9D wrote:

I keep getting error messages when trying to log to my HRD logbook. If the logging program is open then I can log to the Access database. But not if the logbook program is closed.


I haven’t had this problem before but I do now for some reason. I checked all the parameters and they are correct according to a previous post regarding the matter. I’m guessing the fix is something easy but I can’t find it.


I don’t have the error message so don’t ask for it. The version of the HRD Logbook is the current

HRDLogbook needs to be running. This is highlighted in the Help file. It has always been the case, it is not new.

Logging is done via the TCP interface of HRDLogbook, if HRDLogbook is not running there is nothing listening on the TCP port to accept the logging instruction. The only exception is with HRD5 & HRD6.2 (and earlier) where logging is done via direct writes to the log database file as there is no TCP interface available with those very old versions.

de Laurie VK3AMA

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