Date   
Re: Double in the log...

Bob
 

Steph, are you sure? Look in your logbook and see what is in the RST_RCVD field. SeventyThree(s).

On October 9, 2019 at 8:48 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

 



 


 

Re: Edit Errors

HI3B Radhames
 

I think you're right and in one of my previous messages, I had already said the same yesterday. It seems to be in my case the only practical solution because the issue is not persistent. because  It happens sometimes and other times not while doing the same. Anyway, I sincerely regret the time you have spent, and I will repeat the same procedure for the last time, but with extreme care,  following your recommendations yesterday. It will confirm that the problem is mine, rather than your program...Have you good day Bob and excuse me for any misunderstanding and we keep in touch. 73


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Wednesday, October 9, 2019 3:15 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

Rada, I have spent many hours trying to duplicate your problem. I can not break it. Maybe in your case it is better if you export the log to an ADIF file, make the corrections, make a new/empty logbook an import the corrected ADIF file. I have no other suggestions. Now to bed. SeventyThree(s).

On October 8, 2019 at 7:13 PM HI3B Radhames <hi3b@...> wrote:

--
HI3B

Re: Edit Errors

YV5EN - Edwin
 

Hi Rada.
Please be sure you have checked the hh:mm:ss format.
To do so, please do the following steps:
Go to "Ajustes"
Then, go to "Formato de hora"
Then check the bottom option: 23:59:59

Now you have to check if you have hh:mm:ss duplicated

Cheers

Re: Double in the log...

Steph Collas <f5nzy@...>
 

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

Re: Edit Errors

Bob
 

Rada, I have spent many hours trying to duplicate your problem. I can not break it. Maybe in your case it is better if you export the log to an ADIF file, make the corrections, make a new/empty logbook an import the corrected ADIF file. I have no other suggestions. Now to bed. SeventyThree(s).

On October 8, 2019 at 7:13 PM HI3B Radhames <hi3b@...> wrote:

Re: Edit Errors

HI3B Radhames
 



From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 5:45 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key? Always if the arrow key ... Try the TAB key.

(Excuse me my friend Bob ...I got confused when I answer your question, because I thought and write arrow keys.  I meant say he Tab key. Excuse me again.We know that if we use the arrow keys, instead of the TAB key if it is good for this proposal, it would take a very  long time to move from one field to another. Does not  lógica use the arrow key. 


This is the way the logic works if you change the date or time:


a) Check to see if the new date date/time is already used by another QSO. If it is try 20 times adding one second to the new time to find an unused time. If we fail, show an error message (you do not see this message). In the screenshot you can see that  date/time is repetitivo with a few esos, because I did those contacts inside same minute. Must time when hams are in contest they make many contacts in one minute. I have not use for contest a third party software. All those  Qsos has same date and time. Think if use sometimes your program in contest mode, should increment time in one secad. Then for get save all contacts in L32, I have to increment in one second the time. 


b) Delete the existing QSO


c) Add the QSO using the new time ... This is the problem ...  When we get here there already is a QSO here. It has workd correctly for thousands of users for many years. So we have to find out what is special about your setup. 

I do not believe that my configuration has something special. But, you never knows. I will try to do again what I have always done: change the date, or the time if necessary, or change any other data. But I will do it with EXTREME CARE to see if the problem persists. I'll let you know anything later. Thank you for your time and effort trying to help me. I reiterate my apologies for my confusion and misunderstanding, it was like  a  cable crossed in my mind when I responded you.
I will do it with affraid. Hope thet issue does not come again. I will cross my finges. Thanks my friend. Rada


SeventyThree(s).

On October 8, 2019 at 5:08 PM HI3B Radhames <hi3b@...> wrote:

 
Attention Bob and all:
Extra comments to your last email about Edit Errors.

From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 3:47 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

UPDATE_VIOLATION error message tells me that the QSO is already in the Logbook. It is absolutely logic that if I try to modify one Qso is becase it exist in the Logbook We know it is not in the logbook, so how/why is it trying to do this?  Let me try to make you understand my better: 1) Qso is in the logbook. It is logic and mandato than if I want to delete a contact it is in logbook. Not way to delete Qso than never it has be logged. 2) I try to modify it and 3) Sometimes appear and other times does not the famous error. 4) If the error occurs, the end result is that the contact is deleted and I have to log it again. 5) Before, always, absolutely always, I changed the date of a contact or the time, without any problem. When I say before, I am talking about last year or maybe before.



The Qso is in the logbooklet to be in the logbook sometido I don´t understand well what you are  Thank you for the description of what you do to edit the date. You said this:


3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary.


Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key?Always if the arrow key


Another question. You describe changing the date, then changing the time, then maybe changing the gridsquare, Does the error happen when you change the date, or when you change the time, When I change the date  or when you change the gridsquare.   Never, absolutely never I touch  the gridsquare. I don´t know how to do it. The info about the gridsquare appear as  final result of the error, but not because I have try to make some modification over ir. I have not any reason for change the gridsquare. Beleive me, I don´t know how to do  that.  I have not gone so far, and  my limited experience tells me that this is untouchable information if I find it.  
 
When you read the word "gridsquare" in the box that reports the error, you should understand that it is information prior to the contact being permanently deleted, and it   does not mean that I try to modify the gridsquare. Well, if before I did exactly the same to change date or modify any data of any field of a contact, specially the date, time, call or so on,  and now that happens, my logical conclusion is that it seems to have some conflict inside the structure of L32 or at best of the cases, it could be attributes the problem to an incorrect way mine to modify a contact previously saved in the logbook. If this is the latter and not the first, and if so, I count with your help or that of someone from the forum. In short, what be supone should to do for make correctly any change in the logbook? Hope "Mr. Google Translator" have been good job.. Hi hi hi.
73, 
Rada.


. SeventyThee(s)


On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


 


--
HI3B


 


--
HI3B

Re: Edit Errors

Bob
 

Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key? Always if the arrow key ... Try the TAB key.


This is the way the logic works if you change the date or time:


a) Check to see if the new date date/time is already used by another QSO. If it is try 20 times adding one second to the new time to find an unused time. If we fail, show an error message (you do not see this message).


b) Delete the existing QSO


c) Add the QSO using the new time ... This is the problem ... When we get here there already is a QSO here. It has workd correctly for thousands of users for many years. So we have to find out what is special about your setup.


SeventyThree(s).

On October 8, 2019 at 5:08 PM HI3B Radhames <hi3b@...> wrote:

 
Attention Bob and all:
Extra comments to your last email about Edit Errors.

From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 3:47 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

UPDATE_VIOLATION error message tells me that the QSO is already in the Logbook. It is absolutely logic that if I try to modify one Qso is becase it exist in the Logbook We know it is not in the logbook, so how/why is it trying to do this?  Let me try to make you understand my better: 1) Qso is in the logbook. It is logic and mandato than if I want to delete a contact it is in logbook. Not way to delete Qso than never it has be logged. 2) I try to modify it and 3) Sometimes appear and other times does not the famous error. 4) If the error occurs, the end result is that the contact is deleted and I have to log it again. 5) Before, always, absolutely always, I changed the date of a contact or the time, without any problem. When I say before, I am talking about last year or maybe before.



The Qso is in the logbooklet to be in the logbook sometido I don´t understand well what you are  Thank you for the description of what you do to edit the date. You said this:


3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary.


Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key?Always if the arrow key


Another question. You describe changing the date, then changing the time, then maybe changing the gridsquare, Does the error happen when you change the date, or when you change the time, When I change the date  or when you change the gridsquare.   Never, absolutely never I touch  the gridsquare. I don´t know how to do it. The info about the gridsquare appear as  final result of the error, but not because I have try to make some modification over ir. I have not any reason for change the gridsquare. Beleive me, I don´t know how to do  that.  I have not gone so far, and  my limited experience tells me that this is untouchable information if I find it.  
 
When you read the word "gridsquare" in the box that reports the error, you should understand that it is information prior to the contact being permanently deleted, and it   does not mean that I try to modify the gridsquare. Well, if before I did exactly the same to change date or modify any data of any field of a contact, specially the date, time, call or so on,  and now that happens, my logical conclusion is that it seems to have some conflict inside the structure of L32 or at best of the cases, it could be attributes the problem to an incorrect way mine to modify a contact previously saved in the logbook. If this is the latter and not the first, and if so, I count with your help or that of someone from the forum. In short, what be supone should to do for make correctly any change in the logbook? Hope "Mr. Google Translator" have been good job.. Hi hi hi.
73, 
Rada.


. SeventyThee(s)


On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


 


--
HI3B


 

Re: Edit Errors

HI3B Radhames
 

Bob and all.....
Comments below


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 3:55 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

Is it possible that while your are editing these QSOs in your logbook, you are also logging new QSOs from some external program - like WSJT-X  or some program writing to your logbook? Not....Absolutely no.That happens in the way I have explained it to you, or at least as I have tried to make you understand me better. I noticed that many  Qsos were logged  with the incorrect year. I wrote 1993 instead of 1992. Those contacts are in my old handwritten logbook. I want to modify them  for got  the correct year appears. I neve have open and ready for jogging other logbook or external program like WSJT-X or similar.In fact, I have made very few contacts in this digital mode that I have not imported into L32 yet. I confirm that you: I´m a fan of your program, which almost  does absolutely everything  need  must hams. Very ccasionally I complement the small limitations   of L32 with another application. I am and I think I will always be a fan of this program, which besides being very complete is totally free and has great support in the forum, does not matter it lack of a bit things, possibly not very difficult to implementado in the future for become the perfect jogging programt,  73, Rada


SeventyThree(s).

On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


--
HI3B

Re: Edit Errors

HI3B Radhames
 

Attention Bob and all:
Extra comments to your last email about Edit Errors.


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 3:47 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 

UPDATE_VIOLATION error message tells me that the QSO is already in the Logbook. It is absolutely logic that if I try to modify one Qso is becase it exist in the Logbook We know it is not in the logbook, so how/why is it trying to do this?  Let me try to make you understand my better: 1) Qso is in the logbook. It is logic and mandato than if I want to delete a contact it is in logbook. Not way to delete Qso than never it has be logged. 2) I try to modify it and 3) Sometimes appear and other times does not the famous error. 4) If the error occurs, the end result is that the contact is deleted and I have to log it again. 5) Before, always, absolutely always, I changed the date of a contact or the time, without any problem. When I say before, I am talking about last year or maybe before.



The Qso is in the logbooklet to be in the logbook sometido I don´t understand well what you are  Thank you for the description of what you do to edit the date. You said this:


3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary.


Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key?Always if the arrow key


Another question. You describe changing the date, then changing the time, then maybe changing the gridsquare, Does the error happen when you change the date, or when you change the time, When I change the date or when you change the gridsquare.  Never, absolutely never I touch  the gridsquare. I don´t know how to do it. The info about the gridsquare appear as  final result of the error, but not because I have try to make some modification over ir. I have not any reason for change the gridsquare. Beleive me, I don´t know how to do  that. I have not gone so far, and  my limited experience tells me that this is untouchable information if I find it.  
When you read the word "gridsquare" in the box that reports the error, you should understand that it is information prior to the contact being permanently deleted, and it   does not mean that I try to modify the gridsquare. Well, if before I did exactly the same to change date or modify any data of any field of a contact, specially the date, time, call or so on,  and now that happens, my logical conclusion is that it seems to have some conflict inside the structure of L32 or at best of the cases, it could be attributes the problem to an incorrect way mine to modify a contact previously saved in the logbook. If this is the latter and not the first, and if so, I count with your help or that of someone from the forum. In short, what be supone should to do for make correctly any change in the logbook? Hope "Mr. Google Translator" have been good job.. Hi hi hi.
73, 
Rada.


. SeventyThee(s)


On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


--
HI3B

Re: Edit Errors

Bob
 

Is it possible that while your are editing these QSOs in your logbook, you are also logging new QSOs from some external program - like WSJT-X or some program writing to your logbook? SeventyThree(s).

On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 

Re: Edit Errors

Bob
 

UPDATE_VIOLATION error message tells me that the QSO is already in the Logbook. We know it is not in the logbook, so how/why is it trying to do this?  Thank you for the description of what you do to edit the date. You said this:


3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary.


Please tell me how you move to the next field? How do you do this - with the mouse, the arrow key, the tab key?


Another question. You describe changing the date, then changing the time, then maybe changing the gridsquare, Does the error happen when you change the date, or when you change the time, or when you change the gridsquare. SeventyThee(s)


On October 8, 2019 at 2:31 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: " Then I make a click over OK and the following description appears: " Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.

 

 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 

Edit Errors

HI3B Radhames
 

Hi Bob and all again:

I will explain step by step, what I was doing before the errors that appeared later:

1st. From the main Logbook window, I did a click to open the Search box.
2nd.) I this box I  look for by date, by code or by the number of Qso that L32 has already assigned for the Qso that I won't edit.  For example in the picture the first contact of a series or chain that I want to modify, changing the year and in someone rare cases the year and time, increasing it when is necessary.

3rd.) I place the pointer over the date field and make a left click that allows me to make the modification or change. In the case, change the number 3 for the number 2.

4th) I move to the next field. It is the Time (in my case INICIO in Spanish) and makes the change if necessary. If not, then I move until the next field. iIs the Call (in my case INDICATIVO, in Spanish), so that the change made is assumed or executed.

Sometimes doing exactly the same thing, the error appears and other times the error does not appear, with the indicated consequence. It is when that line show empty because be loses all the data, including the QSO number field.   At this point appear the ERROR WINDOWS and I L32 is locked, until I mark OK in the WINDOW ERROR. Doing that, the Qso is permanently deleted and the contact disappears definitively.

5th.)   I check that the Qso was deleted by doing a search again. As the contact was in my written logbook, I have to write it again and renumber all the contacts, so that it occupies its exact place, in order of date and time. 

6th.)  The full text of the error message (including the top line), varies in terms of the long string of numbers, and says so (sic):
"db Write Error: VIS_dUPDATE_VIOLATION (the title), followed in some cases by" Error modifying the GRIDSQUARE with the following data: "Then I make a click over OK and the following description appears:" Unable to add modified record with primary key: 33873.16875 ". Other times appear another number of the primary key as 33873   1590277778, and so on.

 It is the best I can explain. I suppose different numbers could continue to appear every time.

I have always understood was the unique and correct way to modify or edit a Qso. If there were another one, I would appreciate your suggestion to me it. 

I had always done it that way, without any problem, with other old versions of L32. I don't have absolute knowledge about programming, but I think the issue could be typical of bad and unexpert user like me, and not caused for internal issues of this version or  previous ones.

Thanks for all.
73,
Below your recommendations.


 It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).




Sent from my Verizon, Samsung Galaxy smartphone

--
HI3B

Re: Extra explanation

Bob
 

Rado, yes you can export your logbook in ADIF, make whatever changes you like and import the file into a new empty logbook. But That should not be necessary. When changing the date or time, Logger32 checks to see if the new value is already assigned to another QSO. If it is, Logger32 automatically adjusts the time to an unused value. SeventyThree(s).

On October 8, 2019 at 12:14 PM HI3B Radhames <hi3b@...> wrote:

Bob and the group:

It is very likely that I did made serious mistakes, trying to edit many dates and times data, ved  with typing errors. Could be possible transfer export all the ADIF  entire file to a notepad, make change one bye one,  and later import the same file, already corrected?
I think that a conflict arises when two Esos coincide with the same date and time, because I do not understand that there is a way to increase the time, and thus avoid the conflict.
73,
Radhames, HI3B


 


--
HI3B


 

Re: Edit Error (See screenshot)

HI3B Radhames
 

Ok.
I will say you, step by step what I do.
Rada


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 12:14 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Error (See screenshot)
 

It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).

On October 8, 2019 at 12:01 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob:

Thanks  for your explanation but:

1st)  Logger32 looks is i not behaving consistently, because many times it allowed me to change the date and, times and other data, and  it does not produced the error that I reported to the group. 
2nd.) I would appreciate if you would recommend the correct way to edit, without the risk of deletion, of a previously saved Qso.
 
Please ignore my ignorance. Consider me a novice user of your program, trying to get to know it better every day.
73,
Rada, HI3B


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 8:45 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Error (See screenshot)
 

33873.16875 = Sep 26 1992 at 04:03:00

33873.1590277778 = Sep 26 1992 at 03:49:00


At the top of the error message is the text db add Error : followed by the reason code of why Logger32 could not change the date. SeventyThree(s).


On October 8, 2019 at 8:05 AM HI3B Radhames <hi3b@...> wrote:

Hi All:

 
Trying to edit from the Logbook Window one by one, the data of a group of Qsos saved with errors in the date,   what appeared  in the attached files.  It occurred several times and the contact was permanently deleted, and I had to enter it again from my hand written logbook.
Does anyone know why this happens? The string of error numbers was different each time and the mention of the gridsquare was repetitive. 
 I don´t know what means  each time: " Unable to add modified record with primary key: 33873.16875," ........."primary key: 33873. 1590277778" and  so on.   And I don't know what it means either "Error modifying  the GRIDSQUARE with the following data: .
I don't know another best way to edit. 
Be understanding, I don't have enough basic experience with the Window operating system. 
Thanks in advance for any help or suggestion.
73,
Radhames (Rada), HI3B
 




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


 


--
HI3B


 


--
HI3B

Re: Edit Error (See screenshot)

Bob
 

It would help if you would tell me the complete text of the error message (including the top line). This would tell me why Logger32 could not write the new date/time into the logbook. What exactly do you type when changing the date or time. For example if you have a QSO with the time or 01:23 and you want to change it to 12:34. You click on the time and the color changes. You erase the 01:23 and type in 12:34. Now exactly what do you do? What do you type now, or where do you click the mouse? SeventyThree(s).

On October 8, 2019 at 12:01 PM HI3B Radhames <hi3b@...> wrote:

Hi Bob:

Thanks  for your explanation but:

1st)  Logger32 looks is i not behaving consistently, because many times it allowed me to change the date and, times and other data, and  it does not produced the error that I reported to the group. 
2nd.) I would appreciate if you would recommend the correct way to edit, without the risk of deletion, of a previously saved Qso.
 
Please ignore my ignorance. Consider me a novice user of your program, trying to get to know it better every day.
73,
Rada, HI3B


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 8:45 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Error (See screenshot)
 

33873.16875 = Sep 26 1992 at 04:03:00

33873.1590277778 = Sep 26 1992 at 03:49:00


At the top of the error message is the text db add Error : followed by the reason code of why Logger32 could not change the date. SeventyThree(s).


On October 8, 2019 at 8:05 AM HI3B Radhames <hi3b@...> wrote:

Hi All:

 
Trying to edit from the Logbook Window one by one, the data of a group of Qsos saved with errors in the date,   what appeared  in the attached files.  It occurred several times and the contact was permanently deleted, and I had to enter it again from my hand written logbook.
Does anyone know why this happens? The string of error numbers was different each time and the mention of the gridsquare was repetitive. 
 I don´t know what means  each time: " Unable to add modified record with primary key: 33873.16875," ........."primary key: 33873. 1590277778" and  so on.   And I don't know what it means either "Error modifying  the GRIDSQUARE with the following data: .
I don't know another best way to edit. 
Be understanding, I don't have enough basic experience with the Window operating system. 
Thanks in advance for any help or suggestion.
73,
Radhames (Rada), HI3B
 




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


 


--
HI3B


 

Extra explanation

HI3B Radhames
 

Bob and the group:

It is very likely that I did made serious mistakes, trying to edit many dates and times data, ved  with typing errors. Could be possible transfer export all the ADIF  entire file to a notepad, make change one bye one,  and later import the same file, already corrected?
I think that a conflict arises when two Esos coincide with the same date and time, because I do not understand that there is a way to increase the time, and thus avoid the conflict.
73,
Radhames, HI3B

--
HI3B

Re: Edit Error (See screenshot)

HI3B Radhames
 

Hi Bob:

Thanks for your explanation but:

1st) Logger32 looks is i not behaving consistently, because many times it allowed me to change the date and, times and other data, and  it does not produced the error that I reported to the group. 
2nd.) I would appreciate if you would recommend the correct way to edit, without the risk of deletion, of a previously saved Qso.
Please ignore my ignorance. Consider me a novice user of your program, trying to get to know it better every day.
73,
Rada, HI3B


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Bob <k4cy@...>
Sent: Tuesday, October 8, 2019 8:45 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Error (See screenshot)
 

33873.16875 = Sep 26 1992 at 04:03:00

33873.1590277778 = Sep 26 1992 at 03:49:00


At the top of the error message is the text db add Error : followed by the reason code of why Logger32 could not change the date. SeventyThree(s).


On October 8, 2019 at 8:05 AM HI3B Radhames <hi3b@...> wrote:

Hi All:

 
Trying to edit from the Logbook Window one by one, the data of a group of Qsos saved with errors in the date,   what appeared  in the attached files.  It occurred several times and the contact was permanently deleted, and I had to enter it again from my hand written logbook.
Does anyone know why this happens? The string of error numbers was different each time and the mention of the gridsquare was repetitive. 
 I don´t know what means  each time: " Unable to add modified record with primary key: 33873.16875," ........."primary key: 33873. 1590277778" and  so on.   And I don't know what it means either "Error modifying  the GRIDSQUARE with the following data: .
I don't know another best way to edit. 
Be understanding, I don't have enough basic experience with the Window operating system. 
Thanks in advance for any help or suggestion.
73,
Radhames (Rada), HI3B
 




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 


--
HI3B

Re: Edit Error (See screenshot)

Bob
 

33873.16875 = Sep 26 1992 at 04:03:00

33873.1590277778 = Sep 26 1992 at 03:49:00


At the top of the error message is the text db add Error : followed by the reason code of why Logger32 could not change the date. SeventyThree(s).


On October 8, 2019 at 8:05 AM HI3B Radhames <hi3b@...> wrote:

Hi All:

 
Trying to edit from the Logbook Window one by one, the data of a group of Qsos saved with errors in the date,   what appeared  in the attached files.  It occurred several times and the contact was permanently deleted, and I had to enter it again from my hand written logbook.
Does anyone know why this happens? The string of error numbers was different each time and the mention of the gridsquare was repetitive. 
 I don´t know what means  each time: " Unable to add modified record with primary key: 33873.16875," ........."primary key: 33873. 1590277778" and  so on.   And I don't know what it means either "Error modifying  the GRIDSQUARE with the following data: .
I don't know another best way to edit. 
Be understanding, I don't have enough basic experience with the Window operating system. 
Thanks in advance for any help or suggestion.
73,
Radhames (Rada), HI3B
 




Sent from my Verizon, Samsung Galaxy smartphone


 


--
HI3B


 

Edit Error (See screenshot)

HI3B Radhames
 

Hi All:

Trying to edit from the Logbook Window one by one, the data of a group of Qsos saved with errors in the date,   what appeared  in the attached files.  It occurred several times and the contact was permanently deleted, and I had to enter it again from my hand written logbook.
Does anyone know why this happens? The string of error numbers was different each time and the mention of the gridsquare was repetitive. 
 I don´t know what means  each time: " Unable to add modified record with primary key: 33873.16875," ........."primary key: 33873. 1590277778" and  so on.   And I don't know what it means either "Error modifying  the GRIDSQUARE with the following data: .
I don't know another best way to edit. 
Be understanding, I don't have enough basic experience with the Window operating system. 
Thanks in advance for any help or suggestion.
73,
Radhames (Rada), HI3B
 




Sent from my Verizon, Samsung Galaxy smartphone

--
HI3B

Re: QRZ kookups internal

larry fields
 

ok will work on this and let you know what happens

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz
DX1PAR HF NET  7095.00 khz & 7165.0 khz
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08) HT Satellite (-02)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY













On Tue, Oct 8, 2019 at 2:50 AM Rick Ellison <rellison@...> wrote:

Ok that’s the latest version..

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of larry fields
Sent: Monday, October 7, 2019 10:44 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] QRZ kookups internal

 

this one

 

Thanks and 73

Larry Fields: du1/n6hpx

Manila PHILIPPINES

 

Retired looking for more work

Office:(63)46-571-5687

cell:    (63)916-756-7781

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

member:

American Radio Relay League W1AW

Philippine Amatuer Radio Association DX1PAR

Philippine Radio Pyramid Society DX1PRS 

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

owner:

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

LICENSED HAM RADIO OP:

DX1PRS GROUP 145.340 mhz

DX1PAR HF NET  7095.00 khz & 7165.0 khz

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

DU1/N6HPX:QRX DX1PAR 7095

DX1PRS 7165 khz evening

DX1PRS 145.340 mhz

DX1L 431.9,

SIMPLEX 144.6, 145.600

2M 144.225 SSB ,

APRS n6hpx(-08) HT Satellite (-02)

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

SATELLITE:

APRS N6HPX-2 GATEWAY

 










 

 

On Tue, Oct 8, 2019 at 2:13 AM Rick Ellison <rellison@...> wrote:

What version of the lookup are you using?? (Setup/About)

 

Next Click Setup/Open Setup. When the window opens select which lookup you are using. (Http=Free, XML=Paid)

Double check your username and password on that window and correct anything that is wrong and then click save.

Try another look up and see if it works for you. If you get the same message

1.       Double check your username and password on QRZ.

2.       If still not working click Setup/Debug/Debug on.

3.       Try another lookup after the lookup fails turn debug off

4.       In the directory where the lookup is installed you will find a file called L32LookupsDebugLog.txt attach that to an email to so I can see where it is failing..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of larry fields
Sent: Monday, October 7, 2019 9:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] QRZ kookups internal

 

emailed just now

 

Thanks and 73

Larry Fields: du1/n6hpx

Manila PHILIPPINES

 

Retired looking for more work

Office:(63)46-571-5687

cell:    (63)916-756-7781

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

member:

American Radio Relay League W1AW

Philippine Amatuer Radio Association DX1PAR

Philippine Radio Pyramid Society DX1PRS 

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

owner:

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

LICENSED HAM RADIO OP:

DX1PRS GROUP 145.340 mhz

DX1PAR HF NET  7095.00 khz & 7165.0 khz

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

DU1/N6HPX:QRX DX1PAR 7095

DX1PRS 7165 khz evening

DX1PRS 145.340 mhz

DX1L 431.9,

SIMPLEX 144.6, 145.600

2M 144.225 SSB ,

APRS n6hpx(-08) HT Satellite (-02)

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

SATELLITE:

APRS N6HPX-2 GATEWAY

 









 

 

On Tue, Oct 8, 2019 at 1:52 AM Rick Ellison <rellison@...> wrote:

Send me a screenshot so I can take a look and compare the sourcecode to the error.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of larry fields
Sent: Monday, October 7, 2019 9:45 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] QRZ kookups internal

 

The message that keeps coming up says the user name and password is wrong even after I attempt to add it.

 

Thanks and 73

Larry Fields: du1/n6hpx

Manila PHILIPPINES

 

Retired looking for more work

Office:(63)46-571-5687

cell:    (63)916-756-7781

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

member:

American Radio Relay League W1AW

Philippine Amatuer Radio Association DX1PAR

Philippine Radio Pyramid Society DX1PRS 

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

owner:

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

LICENSED HAM RADIO OP:

DX1PRS GROUP 145.340 mhz

DX1PAR HF NET  7095.00 khz & 7165.0 khz

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

DU1/N6HPX:QRX DX1PAR 7095

DX1PRS 7165 khz evening

DX1PRS 145.340 mhz

DX1L 431.9,

SIMPLEX 144.6, 145.600

2M 144.225 SSB ,

APRS n6hpx(-08) HT Satellite (-02)

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

SATELLITE:

APRS N6HPX-2 GATEWAY

 








 

 

On Mon, Oct 7, 2019 at 5:01 PM Rick Ellison <rellison@...> wrote:

The next time you get an error message take a screenshot of it and send it to me. At rellison@...

 

73 Rick n2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of larry fields
Sent: Monday, October 7, 2019 3:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] QRZ kookups internal

 

i add the program but which worked for quite a bite this morning but then came up later saying its missing a module. When I try to add the info on a callsign it pops up and blocks my attempts toad the info even manually. And yes I went into the program to get it going the first time. Now I am getting a message saying it needs Updating which I am doing at this moment. 

 

Thanks and 73

Larry Fields: du1/n6hpx

Manila PHILIPPINES

 

Retired looking for more work

Office:(63)46-571-5687

cell:    (63)916-756-7781

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

member:

American Radio Relay League W1AW

Philippine Amatuer Radio Association DX1PAR

Philippine Radio Pyramid Society DX1PRS 

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

owner:

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

LICENSED HAM RADIO OP:

DX1PRS GROUP 145.340 mhz

DX1PAR HF NET  7095.00 khz & 7165.0 khz

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

DU1/N6HPX:QRX DX1PAR 7095

DX1PRS 7165 khz evening

DX1PRS 145.340 mhz

DX1L 431.9,

SIMPLEX 144.6, 145.600

2M 144.225 SSB ,

APRS n6hpx(-08) HT Satellite (-02)

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

SATELLITE:

APRS N6HPX-2 GATEWAY

 







 

 

On Sun, Oct 6, 2019 at 10:40 PM larry fields via Groups.Io <n6hpx1=gmail.com@groups.io> wrote:

Good morning all, and thanks for the info on this, I was kinda figuring it was that but wanted to make sure. I got up to 102 checks before it closed the door on me. I will add the payment so I can  continue. The only sad part the info won't allow me to add the counties of the states I made contact with. which would come in handy in working all counties awards.

 

Thanks and 73

Larry Fields: du1/n6hpx

Manila PHILIPPINES

 

Retired looking for more work

Office:(63)46-571-5687

cell:    (63)916-756-7781

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

member:

American Radio Relay League W1AW

Philippine Amatuer Radio Association DX1PAR

Philippine Radio Pyramid Society DX1PRS 

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

owner:

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

LICENSED HAM RADIO OP:

DX1PRS GROUP 145.340 mhz

DX1PAR HF NET  7095.00 khz & 7165.0 khz

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

DU1/N6HPX:QRX DX1PAR 7095

DX1PRS 7165 khz evening

DX1PRS 145.340 mhz

DX1L 431.9,

SIMPLEX 144.6, 145.600

2M 144.225 SSB ,

APRS n6hpx(-08) HT Satellite (-02)

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

SATELLITE:

APRS N6HPX-2 GATEWAY

 







 

 

On Sun, Oct 6, 2019 at 2:57 PM Phill Morris (G6EES) <Phill.morris@...> wrote:

Larry

 

Based on what you have written below, it is asking for your normal login user name and password that you already have for QRZ.com

 

Note that the free access to QRZ.com only allows up to 100 lookups per day. (actually, I thought it was 50 per day)

You will very easily and quickly go over 100 😊

 

To be able to lookup more than 100 you have to pay QRZ.com

This costs $29.95 per year (or $119.97 for 5 years).

You then have no restriction on how many callsigns you look up 😊😊😊

 

Phill

G6EES

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of larry fields
Sent: 06 October 2019 15:30
To: hamlogger@groups.io
Subject: [hamlogger] QRZ kookups internal

 

I loaded the software and been adding the info like grids and others. But I notice on the internal it shows a error where it needs a password and log in user name. 

question is this one that comes from our regular log it one from the QRZ Page or one we need to make up. 

Bad part of the external is it stops me at 102 look ups.

Thanks.

 

Image removed by sender.

Virus-free. www.avast.com