locked Re: JtAlert Not Logging to HRD or N3jhp #FT8


Brian (N2MLP)
 

Just go to each setting

The DSN address is set wrong use the correct ODBC DSN for your HRDLogbook

========================

         de N2MLP Brian

       Monroe County PA

 

 

========================

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ken Hendrickson
Sent: Thursday, June 21, 2018 5:01 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JtAlert Not Logging to HRD or N3jhp #FT8

 

That is not too much help.

 

On Thu, Jun 21, 2018 at 1:14 PM Brian (N2MLP) <n2mlp@...> wrote:

You have a setup problem

 

========================

         de N2MLP Brian

       Monroe County PA

 

 

========================

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ken Hendrickson
Sent: Thursday, June 21, 2018 1:27 PM
To: Support@HamApps.groups.io
Subject: [HamApps] JtAlert Not Logging to HRD or N3jhp #FT8

 

JTAlertx has quick logging to my HRD logbook. I installed the latest version 2.11.5. I have the latest Wsjt-x and HRD. I get this message when trying to log to HRD. This message repeats itself over and over again until I close JTAlertx

FAILURE : QSO Not logged!

 

ERROR Message : HRD : Unsupported ODBC DSN

 

Callsign :  KI0E

Frequency :  18.101551 MHz

Logged Mode :  FT8

 

This message has been placed in the Windows clipboard.

 

HRD TCP Logging command result returned =>

Ken Hendrickson - w6bzy

 

 

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