Log4OM

Terry,
I am seeing strange things happening with the QSO database, i.e. the CNTY (county) field. When I started using Log4OM, about 3 years ago, the CNTY field contained the county name as specified in the older ADIF 2.x. With later versions 2.2.x and now version 3.x the CNTY field structure has changed. The field now should contain the state abbreviation and county name. Or the primary administrative in one field and the secondary administrative in a second field.

I am seeing some really strange things happening with the database. Look at the attached file. Some of the CNTY fields are in ADIF 2.x format and some are now in an unknown format. It does not even resemble ADIF 3.x format.

Example of a properly formatted CNTY according to old ADIF version 2.x : Lake.
Example of a properly formatted CNTY according to ADIF version 3.x : IL,Lake.
Example of what is happening to the CNTY field now: IL,LAKE // Lake

The way the CNTY field is now makes it hard for county hunters to use this field.

Any light you can shed on this topic would be greatly appreciated. Can't wait for Log4OM V2.

What is your Windows OS and what version of Log4OM are you using?

As you can see from the screen shot I dont have that Issue!

I am seeing the same thing for U.S. counties. I am using Windows 10 version 1903 and Log4OM version 1.40.

Roy KW4G
Sebring, Florida USA

Have either of you tried deleting the data in the counties fields and then doing an Update in the QSO manager

Will take only a few minutes to delete but update may take a bit longer

Terry,
I'm using Win10 and Log4OM 1.40. The problem has existed for several versions of Log4OM.

I'm going to build a test database and I will update you on my findings.

73,
Ken, ac5ez

Terry,

Doing a global update is not always practical sense many hams in the US get net vanity calls signs. I have done updates on a few entries and the CNTY field populates with the county name as expected. But if I use the QSL Archive function and make a change to some other field when the refresh is performed some CNTY entries get changed.

As I said earlier, I'm going to build a test database and see if I can document what is happening. Hopefully.

Take care.
Ken, ac5ez

G4POP wrote: 21 Nov 2019, 12:22 Have either of you tried deleting the data in the counties fields and then doing an Update in the QSO manager

Will take only a few minutes to delete but update may take a bit longer

I have not. I am still learning this software.

Roy KW4G

Terry,

I have been able to document a process that will take good county data and change it into unusable information. I will email you the procedure I used along with screen shots of the process.

73,
Ken, ac5ez