Date   

New version running

py3og@...
 
Edited

Thanks for QSO Relay new version. Syncronization is ok. Before it was 35 minutes to syncronize and now about 15 secon


73, Clovis- PY3OG


Re: Sync not working on v1.2

Hank W6IR
 

I concur that sync is not working in the new version. The entire sql.lite DB was wiped out under the new version. Removed it and reinstalled 1.1 and re-synced. Everything is back in the DB. Will wait for a fix. Chris, I'm happy to help test anything new out, I'm retired from the IT world so I do know my way around.


Hank


Re: New version and DB

Morris WA4MIT
 

Hi Chris I am seeing what the others that have posted the log does not show any relay rows and if I open the delete function no contacts are shown. I did not delete anything just ran the update and then the sync function which stays on no more than 10 seconds. JTAlert is not showing any B4`s here and I looked up a callsign and it should have been a B4 contact in alert. Should we delete the old DB and go from there?. Thanks 73 wa4mit Morris


2017-05-12 06:26:40.0177 Synchronise databases started

2017-05-12 06:26:44.7023 HRD Logbook contains 23320 rows

2017-05-12 06:26:47.4967 Time elapsed: 00:00:07.4789179

2017-05-12 06:26:47.5227 Synchronise databases finished



Re: Sync not working on v1.2

Rick
 
Edited

Chris,

I had verified the paths and had actually read your pdf on configuring QSO Relay for Microsoft Access Database before installing the new version. My post #66 shows the log of the sync.

Rick WB7BOW 73


Re: Sync not working on v1.2

ON4VT Danny OT4V <danny@...>
 

Rick
 
Same issue here .... the QSOrelay DB has not declined in size though ....  But when trying to DELETE a QSO via QSOrealy it shows NO QSO's
 
The "B4" function in JTAlert also doen't see any B4 QSO ....  


Re: Sync not working on v1.2

Chris VK2BYI
 
Edited

There are two data paths involved - relaying JT-mode contacts from QSO Relay to HRD Logbook, and downloading all contacts from HRD Logbook to QSO Relay.  The first path requires the IP Address, TCP Port and Logbook Database values in the QSO configuration settings to be correct, and the second path requires the Connection String setting to be correct.  It may be that your connection string setting is not correct.
Please refer to the Configuring QSO Relay for Microsoft Access Database document in the files section, or on my web site on the QSO Relay page for much greater detail on these related settings.
Let me know how you get on, but due to family commitments, I may not be able to reply again until about 4:00 PM tomorrow my time.
73 Chris
VK2BYI


Sync not working v1.2

Rick
 

Chris,

Just read about the sync log, so here is mine:

2017-05-12 05:11:33.0761 Synchronise databases started
2017-05-12 05:11:33.7181 HRD Logbook contains 4890 rows
2017-05-12 05:11:38.0793 Time elapsed: 00:00:05.0032000
2017-05-12 05:11:38.0793 Synchronise databases finished

Notice it does not show that it was synced in the QSOrelay db

--
Rick Horton  WB7BOW 73


Sync not working on v1.2

Rick
 

Chris,

Installed new version and everything seems to work with the logging, but when I try to sync the databases it deletes all the records in the QSOrelay db as though I did not have any records in my HRD db.  Tried several things but with all the same results.  I have verified that it is pointing to the correct HRD db, and since it is logging properly that should not be a problem.  Using HRD 6.4.0.647.  Any help would be deeply appreciated.

Rick



Re: New version and DB

Chris VK2BYI
 

Look in your Documents/QSORelay folder and you should see a file called "Sync Report yyyyMMddHHmmss.txt" where "yyyyMMdd" is the date and "HHmmss" is your local time when the sync was run.

This file will tell you how many rows there were in HRD when the extract started, and how many rows where synchronised by QSO Relay.  The number of rows should be the same in both cases.

Here is an example with a fairly small dataset.  We have tested this release with a 100,000 row dataset which takes about 3 minutes to sync.  So 5 seconds may be your new normal sync time!

2017-05-12 17:07:39.6239 Synchronise databases started
2017-05-12 17:07:39.7648 HRD Logbook contains 1298 rows
2017-05-12 17:07:40.9863 1298 rows synchronised in QSO Relay
2017-05-12 17:07:40.9868 Time elapsed: 00:00:01.3629135
2017-05-12 17:07:40.9868 Synchronise databases finished

Your database size would probably come down a bit in size if it was 'compacted', but it doesn't need to be.  The differences in file sizes are more a indication of the different file formats, rather than the actual size of the data.

73 Chris,
VK2BYI

PS: To all reading this post - I forgot to mention the 'Sync Report' in the updated QSO Relay v1.2 documentation.  I will update it and post it online over the weekend sometime.


New version and DB

Morris WA4MIT
 

Guys thanks very much for your effort and for sharing this with the HRD community. I have installed the new version and since I was using the old version my DB was in place. Syncing had taken over an hour is now 5 seconds. When looking at my HRD db it is 80,240kb the relay db is 19,272 kb. Does this sound about right? I know it seems to be working OK was just curious about the size difference. Again thanks guys you have really helped the HRD JT user community. 73 Morris wa4mit 


locked QSO Relay - Release 1.2 Now Available

Bruce VK2RT
 

Please be advised that a new release of QSO Relay (Version 1.2) is now available at http://www.vk2byi.com.au/qsorelay/

We wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.

Release Notes for Version 1.2

  • Improved Database Synchronisation performance;
  • Added Database Synchronisation reports to users “Documents\QSORelay” folder;
  • Added caching of contacts that could not be relayed to HRD Logbook, to allow relay during a subsequent database synchronisation;
  • Improved message description on unique constraint violation exceptions;
  • Floating point values in float columns that should only contain integer values, are converted to integers;
  • Added row count to Delete Contact dialog caption bar;
  • Added QsoDate and Call search feature to Delete Contact dialog;
  • Added multiple attempts to check contact has been successfully logged in HRD Logbook;
  • Added support for different decimal place characters for different cultures;
  • Added support to convert invalid floating point values to integers values;
  • Added diagnostic tracing statements that can be captured to a session log file;

Please ensure that you download and read the new documentation.

If you are in need of a more detailed explanation on how to correctly configure QSO Relay when HRD Logbook is using a Microsoft Access (.mdb) database, we have added a new document called "Configuring QSO Relay for Microsoft Access Databases".

QSO Relay users, please spread the word...


Re: QSORELAY and error msg

Chris VK2BYI
 

We have identified an issue where QSO Relay is trying too soon to verify that the contact was logged after requesting HRD to log it, and not allowing enough time for HRD to actually write the contact to the database.  You get the warning but the contact subsequently appears in HRD Logbook.


We have modified the code to try more than once over a number of seconds to verify the contact, and this should address this problem.


It will be available in a new release that we are working on at the moment and hope to release shortly as time permits.


73 Chris

VK2BYI


QSORELAY and error msg

Morris WA4MIT
 

It seems that after a few hours use that qsorelay and or jtalert is loosing contact with the DB I am getting error QSO not logged msg when in reality the contact is logged. This has happened couple of times now. yesterday I left JTDX, JTAlert and QSORELAY all on but JTDX was stopped from decoding when I came back to computer it had lost contact and would not log QSO`s on same msg restarted the softwares all OK again. Really do appreciate the software being able to use latest HRD is great thanks guys. 73 Morris WA4MIT


Re: Backups

Bob Davet
 

Chris:

 

OK. I have deleted all my logs that were in there.

Created a new one and restored all the data. It is all there.

 

Configured it with the new log. Test connection successful.

 

Synchronize the data base and get the same issue. Last entry in the QSORelay SQLite db is 5/29/2015. There are entries for 2016 and 2017 that are not showing up in the Delete Contact box.

 

Hope you have some more ideas?

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris
Sent: Saturday, May 06, 2017 7:56 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Backups

 

No problem at all Bob.  Happy to help.

Chris
VK2BYI


Virus-free. www.avast.com


Re: Backups

Chris VK2BYI
 

No problem at all Bob.  Happy to help.

Chris
VK2BYI


Re: Backups

Bob Davet
 

Chris:

 

I really appreciate all your help.

 

I have tried selecting other log books in HRD and QSORelay. All the results come out the same. They stop at that 2015 Date.

 

I am on my way out the door to go to work. I’m a Firefighter/Paramedic. I will be on my 24hr shift and out of communication with my home computer.

I have a couple things I want to try when I get home. So don’t think I’m ignoring you.

 

All the log books I have (3) all read the same data. They have all the QSO’s, but when I try and sync them they only go thru 2015.

 

Talk to you when I get back.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris
Sent: Friday, May 05, 2017 11:22 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Backups

 

Hi Bob,

The following screen capture shows the the 'Access - W8RID' database tab for the ODBC definition I created to open your Access .mdb file, and after I restored the latest XML backup file you sent, it now contains all of your 1,754 contacts up to 2017-04-30 21:28:30:

However, the .mdb file you sent me previously only had 1,258 contacts up to 2015-05-29 12:25:15 as previously posted in your 'not_showing_all_contacts_in' topic.

So, I believe that you may have selected the wrong HRD Logbook database in the QSO Relay configuration settings, as it appears as though QSO Relay is fetching the 1,258 rows from a different Access database file.

The text on the tab of the open database in HRD Logbook - Access - W8RID', comes from the Title in Logbook Databases dialog in HRD:

As you can see in the following screen capture, the Logbook Database: drop down listbox In the QSO Relay configuration dialog lists of the database titles defined in HRD Logbook:

You need to make that the selected database in QSO Relay matches the same database that is currently being used in HRD Logbook.  I believe you should then be ready to go, as I was able to successfully synchronize all 1,754 contacts this time.

This is the new Delete Contact dialog that will be in the new release coming shortly.  It displays the row count in the caption and also provides an incremental search by QsoDate or Call facility that will make it much easier to locate a row if the one you want to delete is not the most recent:

73 Chris
VK2BYI


Virus-free. www.avast.com


Re: Backups

Chris VK2BYI
 

Hi Bob,

The following screen capture shows the the 'Access - W8RID' database tab for the ODBC definition I created to open your Access .mdb file, and after I restored the latest XML backup file you sent, it now contains all of your 1,754 contacts up to 2017-04-30 21:28:30:

However, the .mdb file you sent me previously only had 1,258 contacts up to 2015-05-29 12:25:15 as previously posted in your 'not_showing_all_contacts_in' topic.

So, I believe that you may have selected the wrong HRD Logbook database in the QSO Relay configuration settings, as it appears as though QSO Relay is fetching the 1,258 rows from a different Access database file.

The text on the tab of the open database in HRD Logbook - Access - W8RID', comes from the Title in Logbook Databases dialog in HRD:

As you can see in the following screen capture, the Logbook Database: drop down listbox In the QSO Relay configuration dialog lists of the database titles defined in HRD Logbook:

You need to make that the selected database in QSO Relay matches the same database that is currently being used in HRD Logbook.  I believe you should then be ready to go, as I was able to successfully synchronize all 1,754 contacts this time.

This is the new Delete Contact dialog that will be in the new release coming shortly.  It displays the row count in the caption and also provides an incremental search by QsoDate or Call facility that will make it much easier to locate a row if the one you want to delete is not the most recent:


73 Chris
VK2BYI


Backups

Bob Davet
 

Here are the last 2 back ups.

Bob

W8RID


Re: Not showing all contacts in delete box.

Bob Davet
 

Chris:

 

My HRD logbook Shows all my contacts.

I will be sending you my last 2 backups. In a few minutes.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris
Sent: Friday, May 05, 2017 11:01 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Not showing all contacts in delete box.

 

Hi Bob,

I opened the Access and SQLite databases you provided and they both contain 1,258 rows.  So all of the rows that are in your Access database have been synchronized in QSO Relay.

I wrote two queries to break down the number of contacts per year for each database, and here are the results for Access and SQLite respectively:

      

As you can see the number of contacts per year are identical.  So I am confident that all of contacts have been sync'ed.

QSO Relay only selects rows from, and inserts rows into, HRD Logbook - it does not delete HRD rows.  The Delete Contact feature only deletes rows one at a time from the QSO Relay database.



So I would have to assume you may have accidently deleted all contacts made after the contact with VK3ERW on 2015-05-29 12:25:15.

 

HRD Logbook creates automatic backups of your database periodically, so you should be able to recover your lost rows if you can locate the archive made immediately before the data loss.


73 Chris

VK2BYI

 


Virus-free. www.avast.com


Re: Not showing all contacts in delete box.

Bob Davet
 

Chris:

 

I have contacts that I made in 2016 and 2017 that do not show.

 

Why are these not there?

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris
Sent: Friday, May 05, 2017 11:01 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Not showing all contacts in delete box.

 

Hi Bob,

I opened the Access and SQLite databases you provided and they both contain 1,258 rows.  So all of the rows that are in your Access database have been synchronized in QSO Relay.

I wrote two queries to break down the number of contacts per year for each database, and here are the results for Access and SQLite respectively:

      

As you can see the number of contacts per year are identical.  So I am confident that all of contacts have been sync'ed.

QSO Relay only selects rows from, and inserts rows into, HRD Logbook - it does not delete HRD rows.  The Delete Contact feature only deletes rows one at a time from the QSO Relay database.



So I would have to assume you may have accidently deleted all contacts made after the contact with VK3ERW on 2015-05-29 12:25:15.

 

HRD Logbook creates automatic backups of your database periodically, so you should be able to recover your lost rows if you can locate the archive made immediately before the data loss.


73 Chris

VK2BYI

 


Virus-free. www.avast.com