开云体育

------ Message d'origine ------

De "Rudolf Klvana" <rud.klvana@...>

? [email protected]

Date 31/10/2024 21:07:39

Objet Re: [hamlogger] Edit OPERATOR

I am not wondering that you do not believe me. I did not believe my eyes when I saw the stuff as well.

Attached there is the original file which was imported in the first step.

I tried to attache the full adif logbook, but it is too big, myaybe the link would help.

Well, I plan a short SOTA activation on two meters FM tomorrow afternoon, typically yielding only a handful of QSOs.

Let me wait and see how it goes.

73, Ruda, OK2QA

?t 31. 10. 2024 v?19:13 odesílatel Bob via <k4cy=[email protected]> napsal:

... of course when you edited the operator <OPERATOR:5>OK2QA to be OK2QA/P you did change the 5 to 7. Oh well, SeventyThree(s)AndBackToGardening.

On 10/31/2024 2:02 PM EDT Bob <k4cy@...> wrote:

?

?

I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).

On 10/31/2024 1:28 PM EDT Rudolf Klvana <rud.klvana@...> wrote:

?

?

Hi,

I have similar problem.

After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.

Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.

Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.

I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.

Help?

73, Ruda, OK2QA

?

Tried similar way as Bob suggests proceeding as follows:

?t 31. 10. 2024 v?16:08 odesílatel Bob via <k4cy=[email protected]> napsal:

Here we go again ...

?

1) Backup your logbook

2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456

3) Export a partial logbook of QSO number 1 to QSO number 123455

4) Create a new/empty logbook

5) Import the file you made in step 3

6) Make a new backup

7) Promise yourself to ALWAYS make backups before importing files.

?

SeventyThree(s).

?

On 10/31/2024 10:55 AM EDT PY2NY <py2ny.vitor@...> wrote:

?

?

Good morning

?

I forgot to change OPERATOR before importing to Logger32.

Now, I would like to edit OPERATOR from PY5WRTC to PY2NY

but seems to me that the only way is one by one...

Is there a way to change all?PY5WRTC to PY2NY at same time?

Thanks again

?

.

..

...

--------------------------------

PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos

?

?

?

?