Announcement

Collapse
No announcement yet.

How to import Custom fields from ADIF file?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to import Custom fields from ADIF file?

    I try to move from Logic9 to HRD. I have to import about 140,000 QSO records with different user specific fields like <ARLHS>, <WCA>, <WWFF>, <MY_ARLHS>, <MY_WCA>, ... It is a feature of Logic9 that I can define many user specific fields with suitable field names for my own purposes.
    Since there is no explanation in the HRD manual or in the wiki how to import user specific fields to the HRD custom fields I made an experiment:
    1) I exported one QSO record of my HRD test logbook. It has the following content
    #++
    #
    # HRD Logbook version 6.7.0.254, Copyright © 2003 - 2019 by HRD Software, LLC
    # https://www.HamRadioDeluxe.com/
    #
    # Created: 20191130 194818
    #
    #--

    <ADIF_VERS:3>2.2
    <PROGRAMID:14>HamRadioDeluxe
    <PROGRAMVERSION:17>Version 6.7.0.254
    <CREATED_TIMESTAMP:15>20191130 194818
    <EOH>

    <a_index:3>0.0 <ant_az:3>0.0 <ant_el:3>0.0 <band:2>2m <call:7>DM3CW/P <cont:2>EU <country:24>Fed. Republic of Germany
    <cqz:2>14 <distance:3>0.0 <dxcc:3>230 <eqsl_qsl_rcvd:1>N <eqsl_qsl_sent:1>N <force_init:1>N <freq:10>145.425000
    <gridsquare:6>JO71AF <app_hamradiodeluxe_heading:3>0.0 <ituz:2>28 <k_index:3>0.0 <lat:11>N000 00.000
    <lon:11>E000 00.000 <lotw_qsl_rcvd:1>N <lotw_qsl_sent:1>N <mode:2>FM <my_lat:11>N000 00.000 <my_lon:11>E000 00.000
    <name:7>STEFFEN <pfx:3>DM3 <qslmsg:47>QTH: GROSSER PICHO, LOC: JO71EC, GMA: DM/SX-037 <qsl_rcvd:1>N <qsl_rcvd_via:1>D
    <qsl_sent:1>N <qsl_sent_via:1>D <qso_complete:1>Y <qso_random:1>N <qth:10>WUESTEBERG <rst_rcvd:2>59 <rst_sent:2>59
    <rx_pwr:3>0.0 <sfi:3>0.0 <sig:3>DOK <sig_info:3>Y30 <station_callsign:7>DL6JZ/P <swl:1>N <time_off:6>091800
    <time_on:6>091800 <tx_pwr:6>20.000 <app_hamradiodeluxe_user_defined_0:8>ABCDEFGH <hrdcountryno:3>230
    <qso_date:8>20160102 <EOR>

    2) Then I tried to import this file into Ham Radio Deluxe again. The result looks like that:

    File ....
    File ...
    Cache ...
    Database ...
    Database Open status 1
    Database Opening table TABLE_HRD_CONTACTS_V01
    Invalid Field <APP_HAMRADIODELUXE_HEADING> is not supported by ADIF (Error) (1 instas
    Invalid Field <APP_HAMRADIODELUXE_USER_DEFINED_0> is not supported by ADIF (Error) (1 instances)

    What do I wrong?

    73
    Wolf, DL6JZ


  • #2
    Hello Wolf,

    Unfortunately the Importing of HRD UserDefined Fields is broken , so until it's fixed you will be unable to import Custom Fields into the HRD Database. See:- https://development.hamradiodeluxe.com/view.php?id=3430
    Regards,

    David G4NVB

    Comment


    • #3
      Hello David,

      thank you for the information. It seems to be an older issue (> 3 months?). So I have to use Logic9 furthermore. It's a pity.
      And I will spread the word in the german forum also. There is an unanswered topic on dealing with custom fields also.

      73
      Wolf, DL6JZ

      Comment


      • #4
        Guten Tag Wolf,

        I think this issue manifested itself around Ver 6.4 / 6.5. I've been aware of it for over 6 months and the Mantis 3463 was raised 4 months ago.
        Regards,

        David G4NVB

        Comment


        • #5
          Hello David again,

          why did I pay my money for such a software torso?? I believe I wouldn't get the money back if i would make such a request. So may be I will find a work around. Some SQL-statements including string-functions would do it.

          But I can not understand what makes it so difficult to repair such a simple peace of software like an import routine for text-files.

          73
          Wolf, DL6JZ

          Comment


          • #6
            Guten Tag Wolf,

            I also use MySQL Database and have found a nice utility (MySQL-Front www.mysqlfront.de) that exports the MySQL File in Excel Binary Format. I then modify the Spreadsheet and then Import the Binary File back into the MySQL Database, maybe an option for you?

            HRD Logbook saves UserDefined Fields to the Database and will export them ok, just not able to Import.

            http://mysql-front.freedownloadscenter.com/windows/
            Last edited by G4NVB; 12-03-19, 15:37. Reason: New Link added
            Regards,

            David G4NVB

            Comment


            • #7
              Hello David,

              thank you very much for this information on mysqlfront.de. My first approach is a bit different. I want to use the Access-Database in HRD. But this is not the difference.

              I would prepare my source database in Logic9 (FoxPro) in such a way that all the content of the user specific fields is stored in standard ADIF fields, e. g. <comment>.
              Then I can export my log from Logic9 and import the ADIF file to HRD.
              After that I can extract the content of the different user specific fields with MS Accees tools to their right places in the HRD database.

              But may be I will switch to Maria/MySQL DB and follow your way. This one seems to be a bit easier.

              73
              Wolf, DL6JZ

              Comment


              • #8
                Guten Tag Wolf,

                I didn't realise there was a Logbook (Logic9) that uses FoxPro; I use "Visual Fox Pro" for my "Front End" to MySQL Database.

                Hopefully the HRD ADIF Import will be sorted in due course.

                Regards,

                David G4NVB

                Comment


                • #9
                  I found a work-around which seems to be a bit more comfortable:

                  1. Opened HRD Logbook with the empty Database and identified logbook field which are nor used in my old logging software. There are a lot of them (CONTECTED_OP, MY_CNTY, PUBLIC_KEY, ...).
                  2. Exported the QSOs from my old logging software into an ADIF file.
                  3. Opened the ADIF file in a text editor and replaced the old user specific field names with appropriate HRD log fieldnames (e. g. Search for "<wff_ref:" and Replace with "<CONTACTED_OP:").
                  4. Imported this modifIed ADIF file into HRD logbook.
                  5. Exit the HRD logbook and opened the .mdb-logfile with MS-Access.
                  6. Transfered the content of the misused HRD logbook fields to the correct fields USER-Defined_FIELD_0, ...
                  7. Exit MS-Access and started HRD logbook.
                  8. All is fine, but this work around for the fail of a simple software feature took me one full day.

                  By the way, I found that there are 10 user defined fields in the database and not only six.Let's see when the other four fields can be used in HRD!??

                  73
                  Wolf, DL6JZ

                  Comment


                  • #10
                    Hi Wolf and David,

                    it's me who asked for the ADIF import of custom fields in the German section of this forum.
                    Wolf's workaround sounds pretty good, I might try that, too.

                    What's also interesting: Is there any documentation regarding the fields inside the HRD database?

                    BTW: Does anyone have experience running HRD with MS SQL Server?

                    73
                    Klaus, DF6NP

                    Comment


                    • #11
                      Guten Tag Klaus,

                      Can't help with MS SQL although I've successfully used MySQL.

                      I should be able to provide you with a list of HRD Fields from my HRD MySQL Database.

                      Regards,

                      David G4NVB

                      Comment


                      • #12
                        Hi David,

                        this would be great.

                        Do you possibly know, which previous version of HRD doesn't have the import bug, so I could downgrade temporarily, do the import and then go back to the current version?

                        Regards es 73
                        Klaus

                        Comment


                        • #13
                          Originally posted by DF6NP View Post
                          Do you possibly know, which previous version of HRD doesn't have the import bug, so I could downgrade temporarily, do the import and then go back to the current version?
                          I am not too sure when the ADIF Importing of User_Defined Fields stopped working; it was reported here:-

                          https://development.hamradiodeluxe.com/view.php?id=3430

                          but had occurred prior to August 2019. It may have been during the Ver 6.5 to Ver 6.6 which was when the new HRD Licensing System was introduced; so it could get messy if you go back too far.

                          Regards,

                          David G4NVB

                          Comment


                          • #14
                            Uh, so I'm stuck to this version. I just licensed HRD back in August, so don't have earlier license keys.
                            Will try the workaround.

                            Thanks a lot
                            73 es Regards
                            Klaus, DF6NP

                            Comment


                            • #15
                              Hi David & Wolf,

                              just a short update.
                              First I converted the HRD Access Database to MS SQL Server 2016 and changed the HRD databse definition to this SQL databse.

                              Then I modified the ADIF file from my old logging software the way you recommended - to import unknown fields into unused fields in the HRD database.
                              In the next step(s) with some simple SQL commands I copied the values from those fields to the corresponding field in the HRD database (i.e. COL_USER_DEFINED_0 for DOK) and set the tmporarily used fields back to NULL.

                              Now everything (as far as I can see now) works like a breeeze.

                              Thanks again fro your help & advice!

                              vy73
                              Klaus

                              Comment

                              Working...
                              X