Hi all,
I am using WL32 version 2.1 under Win98 system. I set the regional setting to Germany, all is working fine. Searching in the databases I found that the if I want to look for 1.8 or 3.5 Mhz standing I will get the 18 Mhz issues for 160 m and nothing for 3.5 Mhz. I found that if I change the decimal point from komma to dot, all works ok. Is there any solution? I would like to keep the German settings. I think the regional settings do not affect the values in the search mask.
73 de Gerald - DL4KG
www.qsl.net/dl4kg
regional settings and DXCC database
-
- Bit of a boffin
- Posts: 67
- Joined: Wed Jan 09, 2002 5:09 am
- Location: Stuttgart, Germany
- Contact:
regional settings and DXCC database
73 de Gerald - DL4KG
-
- Bit of a boffin
- Posts: 67
- Joined: Wed Jan 09, 2002 5:09 am
- Location: Stuttgart, Germany
- Contact:
regional settings and DXCC database
After thinking over I found the solution. You just have to change the entry in the custom list and all works fine.
73 de Gerald - DL4KG
www.qsl.net/dl4kg
73 de Gerald - DL4KG
www.qsl.net/dl4kg
73 de Gerald - DL4KG
regional settings and DXCC database
Thanks Gerald
Yes you guessed correct, the Frequency band is stored in the log database as a pure number and you must adjust the Band List accordingly 1,8 (1.8) and 3,5 (3.5) when using regions that use the comma as a decimal seperator, same goes for entering full frequency band e.g. Mhz,khz (MHz.Khz).
When importing/exporting - its also a good idea to set back your number format in Windows Regional settings to a decimal point, otherwise you may get some corruption of the frequency input/output.
73 Colin G0CUZ
Winlog32 Author
Yes you guessed correct, the Frequency band is stored in the log database as a pure number and you must adjust the Band List accordingly 1,8 (1.8) and 3,5 (3.5) when using regions that use the comma as a decimal seperator, same goes for entering full frequency band e.g. Mhz,khz (MHz.Khz).
When importing/exporting - its also a good idea to set back your number format in Windows Regional settings to a decimal point, otherwise you may get some corruption of the frequency input/output.
73 Colin G0CUZ
Winlog32 Author