QSO Not Saved. Check Band/Mode/Callsign/Date
Posted: 12 Sep 2020, 01:43
Hello,
Using LOG4ON 2 version 2.8.0.0, I recently had some problems updating individual QSOs that were lacking their Grid number. When I tried to do so, Log4OM 2 sent me the following message in red: < QSO Not Saved. Check Band/Mode/Callsign/Date >.
This happened suddenly after about 2000 QSO entered and modified without any problem. The only thing that I did wich was new with WSJT-X was that I recently modified it to use five frequencies on the 60 meters bands for the FT8 protocol.
Is it possible that the fact that I programed more than one frequency for a specific band and mode would generate this error message ? Please note that this error message only appeared for 60 meters QSOs.
If so, how can I correct the database so that I can save the QSO correctly ?
I'm operating a Windows 7 computer with WSJT-X v. 2.2.2 and GridTracker Version 1.20.0906.
Thank you for your help,
Roger
VE2ESF
Using LOG4ON 2 version 2.8.0.0, I recently had some problems updating individual QSOs that were lacking their Grid number. When I tried to do so, Log4OM 2 sent me the following message in red: < QSO Not Saved. Check Band/Mode/Callsign/Date >.
This happened suddenly after about 2000 QSO entered and modified without any problem. The only thing that I did wich was new with WSJT-X was that I recently modified it to use five frequencies on the 60 meters bands for the FT8 protocol.
Is it possible that the fact that I programed more than one frequency for a specific band and mode would generate this error message ? Please note that this error message only appeared for 60 meters QSOs.
If so, how can I correct the database so that I can save the QSO correctly ?
I'm operating a Windows 7 computer with WSJT-X v. 2.2.2 and GridTracker Version 1.20.0906.
Thank you for your help,
Roger
VE2ESF