Yes I have it selected as you pointed out.... I feel a little caught in the middle as you say contact JTAlert and JTAlert says contact you....it is easier for me to update JTAlert manually by clicking

Hi Bruce, I am assume that before you Synchronize Databases, you have 'All Contacts' selected for the Logbook Extract in the QSO Relay options: This means that your entire logbook will be extracted

JTAlert logs perfectly into my HRD log without any problem and I sync the data base without any problem and then I scan and update JTAlert and it seems to work OK except it does not reflect the data

You are most welcome, Roland. Enjoy! 73 Chris VK2BYI

Hi Chris, thank you very much, full ACK. After deleting the file contact.cache in the QSO Relay folder sync is working again. Also I have disabled the Log Address option in JTAlert for now. TU for

Hi Roland, You have a 'cached' contact that QSO Relay is trying to log in HRD Logbook, but can't because it has embedded carriage return/line feed characters (or newlines) in the Address field. There

Hi Chris, I have the exact same problem, running HRD 6.4.0.780. I will zip the QSORelay folder and mail it to you. 73's Roland

hi Antony I find it strange also I have had to go back to JT alert for the time being but when support stops again ?? I too have the My loggbook access under Maria dB and this way before QSO R

Hi, All my contacts are being logged as expected using all the latest program versions including the latest windows10. As has been mentioned I had to produce an empty My Logbook-Access under the Maria

Unfortunately It appears so will see what HRD have to say .... Thank you Chris -- Ic 7300 - Win 10 Pro - WJSTX 1.7 - JTalert 2.94 - HRD 6.4.647 - Maria dB

According to the Session 20170827065143.log file you provided, the QSO with SP8AWL and sent by JTAlert, was received by QSO relay, was saved to the SQLite file used by QSO Relay, and then forwarded on

I have that and had it form day one when HRD suggested that even before QSO relay came into being. Now with prior version of JT alert all worked well until latest version of JT alert will dig into

Hi Jacques, I got the files and from what I can see, your are experiencing a similar issue to that discussed in the HRD Logbook Accepts But Fails To Log Contacts topic. What seems to have worked there

Hi Jacques, Can you please read the Reporting an Issue topic and provide me with the files I need to diagnose the problem? 73 Chris VK2BYI

HI did all as per book all QSO are recorded in the various logs and get looging prompt from JT alert except it is not looged in HRD logbook even with refresh. went over everything UDPs etc but

Thank you...I still do not understand why it worked so well before, but I guess its just a fluke..Anyway, with the current ver> of JTAlert logging directly to HRD is the same as using QSO Relay so Ill

NO. Your approach will not work. What happened is you are witnessing the defect in action. If you keep trying to include the Address field, this will keep happening until the defect in HRD Logbook

woops!!! Now the address appears in the HRD log then blinks off and is gone.. What happened??

It worked!!!! there were blank lines....Ill think abut the work around but I really need the addresses.... seems there may be another approach... If I do the blank line fix every time I do a JTAlert

Hi Bruce, You do have 7 duplicate records in your logbook, but I think you are having trouble locating them because they all have blank values for QSO Date, Time On, Call, Band and Mode. I have added