Dennis,
Not sure if this will help any but here is the SafetyLog file that I was using at the time of the errors. I only used this feature for a very short time so the file is very small.
Note that SafetyLog exported without any errors prior to the share change. When I started LOGic after installing the update here is what I did;
Note all the entries prior to the last two with TM6M were BEFORE the change.
The first TM6M entry (second from the bottom) I manually added LOTW_QSLRDATE, as soon as I moved out of the QSO LogForm, LOGic threw the errors. I closed out of LOGic, did a clean and launched LOGic again.
The second TM6M entry (last one at the bottom) I manually added LOTW_QSLRDATE, moved out of the Logform and LOGic threw the same errors.
So manual changes to existing QSO's seemed to trigger the errors. May not matter at all but I did notice the case of the entries was lower/upper case before the change, after the change the case was all upper. You'll see in the adi file. Also, when I added a LOTW_QSLRDATE I did NOT set the Lotw Rcvd flag to show it was received, also may not matter but worth mentioning.
I'll try logging a new QSO to see if that throws any errors and report back.
Update: Just logging a new QSO also throws the same errors, so not related to changing a prior QSO.
Brad, N8GLS
