On 05/07/2021 7:47 AM Jan <hamlogger@...> wrote:

 

 

I see the same


73
Jan PA4JJ

Op 7-5-2021 om 11:47 schreef Fabio IZ8MBW via groups.io:

I have the same issue if I search for "QSO DATE", but if I search by Callsign it works.

 

 

 

73s

Fabio, IZ8MBW

 

 

 

On Friday, May 7, 2021, 10:57:52 AM GMT+2, Fabien TK5MH <tk5mh@...> wrote:

 

 

Hi all,
I obtain this message when trying to search for a QSO in the logbook
73, Fabien TK5MH

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi zero:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

I see the same


73
Jan PA4JJ

I have the same issue if I search for "QSO DATE", but if I search by Callsign it works.

 

 

 

73s

Fabio, IZ8MBW

 

 

 

On Friday, May 7, 2021, 10:57:52 AM GMT+2, Fabien TK5MH <tk5mh@...> wrote:

 

 

Hi all,
I obtain this message when trying to search for a QSO in the logbook
73, Fabien TK5MH

-- 

____________________________________________________

my dxspider clusters running on a raspberry pi zero:  

pa4jj-2 83.162.186.242 port 7300

pa4jj-3 83.162.186.242 port 7388

On May 7, 2021, at 22:53, Tom Sevart <tmsevart@...> wrote:

On 5/7/2021 03:57, Fabien TK5MH wrote:

Hi all,
I obtain this message when trying to search for a QSO in the logbook
73, Fabien TK5MH

How do you get to that search window?

--
Tom Sevart N2UHC
St. Paul, KS

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

On 05/07/2021 6:56 PM n5kd <n5kd@...> wrote:


Right click in the main logbook window.
It’s the 4th line down.

73’ Pete, N5KD.

On May 7, 2021, at 22:53, Tom Sevart <tmsevart@...> wrote:

On 5/7/2021 03:57, Fabien TK5MH wrote:

Hi all,
I obtain this message when trying to search for a QSO in the logbook
73, Fabien TK5MH

How do you get to that search window?

--
Tom Sevart N2UHC
St. Paul, KS

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

On 05/07/2021 7:32 PM Tom Sevart <tmsevart@...> wrote:


On 5/7/2021 18:10, Bob wrote:

... or you could read/study/learn from the awesome help file/documentation and do two things:

Or you could just be a nice person and answer a simple question. This
program is fairly complex and takes a while to find what could be (and
was) answered very quickly.

--
Tom Sevart N2UHC
St. Paul, KS

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

On 2021/05/10 17:01:33, Fabien TK5MH <tk5mh@...> wrote:

Hi,
I tried to change the regional settings in windows 10 pro but with no success.
I thought the french format for the date could be the culprit but it seems to have no effect on the error.
Sorry Bob to submit one more problem ;-)
But a search on date and time is useful when you receive a QSL for a contact you can't find the callsign in the log.
Just to check it's not a busted callsign

73, Fabien TK5MH

Hi,
I tried to change the regional settings in windows 10 pro but with no success.
I thought the french format for the date could be the culprit but it seems to have no effect on the error.
Sorry Bob to submit one more problem ;-)
But a search on date and time is useful when you receive a QSL for a contact you can't find the callsign in the log.
Just to check it's not a busted callsign

73, Fabien TK5MH

On 2021/05/10 17:01:33, Fabien TK5MH <tk5mh@...> wrote:

Hi,
I tried to change the regional settings in windows 10 pro but with no success.
I thought the french format for the date could be the culprit but it seems to have no effect on the error.
Sorry Bob to submit one more problem ;-)
But a search on date and time is useful when you receive a QSL for a contact you can't find the callsign in the log.
Just to check it's not a busted callsign

73, Fabien TK5MH

On 2021/05/10 21:28:44, Berthoumieux Jean-pierre (F6ITD) <f6itd@...> wrote:

  Fabien and AKI, mon format de date est celui-ci et je n'ai pas de probleme   my date format is this and I have no problem  73

Mailto: f6itd@...

-----E-mail d'origine-----
De: ja1nlx <ayoshida0205@...>
A: Hamlogger <hamlogger@groups.io>
Envoyé le: Lu, 10 Mai 2021 11:00
Sujet: Re: [hamlogger] Error 13 when doing a search in the logbook

Fabien

Please check following steps whether it appears or not.

1. Open Logger32.ini with text editor.

2. Look for [wndLogbookPage Settings] section.

3. Delete all lines in this section.

4. Run Logger32. Logbook page window appears with default settings.

Do you still see error13 ?

73 de aki
JA1NLX

On 2021/05/10 17:01:33, Fabien TK5MH <tk5mh@...> wrote:

Hi,
I tried to change the regional settings in windows 10 pro but with no success.
I thought the french format for the date could be the culprit but it seems to have no effect on the error.
Sorry Bob to submit one more problem ;-)
But a search on date and time is useful when you receive a QSL for a contact you can't find the callsign in the log.
Just to check it's not a busted callsign

73, Fabien TK5MH

On 2021/05/11 15:06:53, Fabien TK5MH <tk5mh@...> wrote:

Hi,
I did the following :

1. Open Logger32.ini with text editor.

2. Look for [wndLogbookPage Settings] section.

3. Delete all lines in this section.

4. Run Logger32. Logbook page window appears with default settings.

 

But no luck! The error13 is still here.  :-(
Sky is falling each time you enter a number for the date in the qso search window but you can manage to have the answer if you acknowledge the error warning each time.
73, Fabien