Search found 5 matches
- 24 Jan 2024, 02:19
- Forum: User support
- Topic: Gridsquares from LOTW
- Replies: 3
- Views: 914
Re: Gridsquares from LOTW
>I think if you check what is provided in the LOTW download that it does not >include the grid as eQSL does Yes, it does. And Log4OM actually updates the database record with the gridsquare information downloaded from LOTW if that field is empty. What it doesn't do is to add the 5th and 6th characte...
- 30 Aug 2022, 10:35
- Forum: User support
- Topic: Gridsquares from LOTW
- Replies: 3
- Views: 914
Gridsquares from LOTW
Hi all, I looked for previous posts about this issue, but found none, so here I am. I download confirmations from eQSL and LOTW to my log, and I am very happy with the way the eQSL download process works: if there is a a Gridsquare in the record, it either extends it with he last two characters if t...
- 16 Jun 2022, 22:50
- Forum: User support
- Topic: Bogus grid squares added automatically
- Replies: 11
- Views: 2061
Re: Bogus grid squares added automatically
Thanks for this, Nolan. Indeed, it was the CTY db that was generating the bogus grid squares. Once I unticked that box, I was able to store QSOs with a blank grid.
- 16 Jun 2022, 12:44
- Forum: User support
- Topic: Bogus grid squares added automatically
- Replies: 11
- Views: 2061
Re: Bogus grid squares added automatically
Jim, thanks for the solidarity :-) Nolan, thanks for the suggestions. I have done a few more tests with v. 2.22.0.0, and then upgraded to 2.22.0.2 as suggested. As far as my tests could go, both behaved the same way with regards to grid squares (I didn't go as far as checking CQ and ITU zones). >Min...
- 15 Jun 2022, 09:46
- Forum: User support
- Topic: Bogus grid squares added automatically
- Replies: 11
- Views: 2061
Bogus grid squares added automatically
Hi all, I'm new in the forum, but using Log4OM for more than a year now. Recently, I started to have problems with bogus grid squares automatically entered into my log. I'm not sure if I changed the settings, or if it is something related to the new version (I only noticed after updating to 2.22.0.0...