Folks, Thanks for bringing this to our attention. We find his comments to be patently false on this subject.
We also note that there are other comments about the .adi output that are not correct. Listed below is a sample output from DXbase 2007 ADIF format. Our format is based upon the ADIF 1.0 specification. You'll note that the QSL_SENT and QSL_RCVD fields contain the "y or n" values as required in the specification. So those who have been posting something to the contrary in other public forums have got it wrong. Perhaps they confused these ADIF fields with other DXbase specific fields ( DXB_QSL_SENT, DXB_QSLRCVD etc...) where we do provide different values for use solely within DXbase. ADIF specifications allow software authors to embed their own "private" fields into an ADIF export for their own use and we, like many other authors do this for the benefit of our customers. Those who import an ADIF file should ignore any fields that are not defined as ADIF specific fields in order to allow for this. If the GlobalQSL service is having difficulty with these DXB_ fields, then they will need to correct their import logic, or you will need to globally remove these fields from your .adi file before sending it to them. As for the QSL_VIA field in ADIF, this field was originally specified in the ADIF v1.0 specification. The value for this field was left open as discretionary data. We, like many others, implemented this field to show whether the card was sent by way of bureau, manager, direct, etc... This has been the way this field was used since the beginning of ADIF nearly ten or more years ago. Recently, some folks defined an updated version of ADIF specification that I think they call v2. In this revised specification, they chose to redefine the QSL_VIA field to be the callsign of the place where a card was sent. In retrospect, they probably should have created a new ADIF field rather than redefine an existing one. But nevertheless, if the receiver of your .adi file has not made allowance for both v1 and also v2 of the ADIF format such that this particular field is properly handled then there could be problems. Either the receiver can fix their code to properly handle both v1 and v2 of the ADIF format, or, the submitter can globally remove this field from their .adi file before sending the .adi file to someone who cannot handle both versions of ADIF. <CALL:5>1A0KM <QSO_DATE:8>19840310 <TIME_ON:6>185500 <RST_SENT:2>59 <RST_RCVD:2>59 <QSL_VIA:6>Bureau <ITUZ:2>28 <OPERATOR:5>AA4LU <PFX:3>1A0 <QSL_RCVD:1>Y <DXBQSL_RCVD:1>1 <BAND:3>15M <CQZ:2>15 <MODE:3>USB <QSL_SENT:1>Y <DXBQSL_SENT:1>1 <QSLSDATE:8>19950402 <DXBPFX:2>1A <DXCC:3>246 <DXBMGRN:1>1 <DXBAWD:1>3 <DXBSEL:1>0 <DXBVAL:1>3 <EOR> ----- Original Message ----- From: "George Harlem W1EBI" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "'DXBase List'" <[email protected]> Sent: Thursday, August 16, 2007 10:58 AM Subject: RE: [Dxbase] A question to all from Joe WA6AXE - GlobalQSL Service I think W3UA's comments are unnecessarily, even unfairly, critical of DXbase. I did a quick test .adi a short time ago and the file appears to conform fully to the ADIF standard. I have had no problems uploading DXbase .adi's to LoTW, so I will predict that they will work fine with GlobalQSL, provided GlobalQSL does the right things with the file. George W1EBI -----Original Message----- From: Carsten Esch [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 11:43 AM To: 'George Harlem W1EBI'; 'DXBase List' Subject: AW: [Dxbase] A question to all from Joe WA6AXE - GlobalQSL Service ... not sure if 'this is enoght' or if the ADI files needs a modification. Paul wrote this morning: Please go and read http://forum.globalqsl.com/index.php/topic,82.0.html I hope this will answer your question, Best 73 Paul 4X6UU ******************************************************************** Regards, Carsten -----Urspr?ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von George Harlem W1EBI Gesendet: Donnerstag, 16. August 2007 17:39 An: 'DXBase List' Betreff: RE: [Dxbase] A question to all from Joe WA6AXE - GlobalQSL Service Great suggestion, Bill. I tried it, and it works FB. The hardest part was unhiding the "Special 1" column that I hid years ago and never used. Now there's a good use for it. George W1EBI -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of FireBrick Sent: Thursday, August 16, 2007 10:34 AM To: DXBase List Subject: RE: [Dxbase] A question to all from Joe WA6AXE - GlobalQSL Service George You can already do this. Not with an icon but what I do, is when I log in bureau cards, put a code in Special1 field. What ever you want to use for the code, perhaps Global??? Then when you want to develop the .adi file, just use the Wizard to select and create a file with only qsos that have Global in the Special1 field. On 8/16/2007 9:21:22 AM, George Harlem W1EBI ([EMAIL PROTECTED]) wrote: > Joe, I would be interested in your responses. I have signed up with > GlobalQSL. They are designing a card for me now. I intend to use it to > reply to bureau cards. However, rather than upload an entire log segment, > I > want to know whether DXbase can add a "Joe-file", or (future release) a > new > icon to click that will allow me to select INDIVIDUAL records to > assemble a > .adi for uploading to GlobalQSL. In other words, say I receive 100 bureau > cards. When I log them into DXbase, I want to highlight the record and, > when I select CFM/Card, I also want to click an icon to add that > particular > QSO to a new database ("GlobalQSL"). When I'm done, I want to use the > Wizard to create a .adi from that new database that I can easily upload to > GlobalQSL. > > Sound reasonable? > > 73, George W1EBI > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Joseph Glockner > Sent: Wednesday, August 15, 2007 11:40 PM > To: DXBase Reflector > Subject: [Dxbase] A question to all from Joe WA6AXE - GlobalQSL Service > > To all: > > Just curious if any DXbase user i ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected]
