Standard Reports, HF Statistics, HF WAS... sure you will see something there ....
Jack ----- Original Message ----- From: "Gary Senesac AL9A" <[EMAIL PROTECTED]> To: "DXbase Reflector" <[email protected]> Sent: Tuesday, January 24, 2006 6:30 PM Subject: [Dxbase] Needed stuff > Are there any standard DXB2006 reports that will show what states are > still > NEEDED for WAS on a specific band or mode? If I use Output/Awards/WAS I > get > a list of what is confirmed, not what is unconfirmed. If I have 40 states > listed for the band or mode (based on Wizard data) then I have to figure > out > what the missing 10. Then, I have to figure out if I worked the missing > states on the band/mode I'm interested in and if the QSL has been sent or > not. > > What would be nice is a report that would print out a row for each of the > 50 > states, whether worked or not. If worked, show the relevant info. If not > worked, just blank fields. I've checked all the standard reports and > can't > find any that are WAS related. Also, there is apparently no way to have > the > wizard filters set to give states worked, but still unconfirmed. > > Gary AL9A > > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > From [EMAIL PROTECTED] Wed Jan 25 09:31:55 2006 From: [EMAIL PROTECTED] (Eric - VE3GSI) Date: Wed Jan 25 09:38:59 2006 Subject: [Dxbase] DXBase import question In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi Dave and other ADIF people, I also use the same combination of WriteLog with DXbase. Yes WriteLog does use the ADIF form of <QTH:n> for a States designation in some contests, but you must remember that for the same contests the exchange for Canadian or DX may be a province or sequence number. WriteLog also uses some special ADIF fields used internally by W/L and are required for tracking the contest. All these special fields are simply ignored by DXbase during an import. One of the advantages of any ADIF file is the ability to use a text editor (WordPad) to simply search and replace. So if you wish, just simple search the ADIF output file from WriteLog for <QTH:2> and replace it with <STATE:2>. DXbase will ignore none U.S. States so nothing is lost except provinces or DX exchange. Also, it is never prudent to import without making at least a temporary back-up file of the main YOURCALL.mdb data file. This is really simple to do, just right click and hold the mouse button your call data file, drag and drop anywhere in the same \FOLDER, release the button and choose COPY. You end up with a neatly labelled file called Copy of YOURCALL.mdb. The labels used in WriteLog are for all Radio Ops around the world, not only for us wishing to track U.S. States. For my own set-up I never do a direct ADIF import from WriteLog (or any programme) without first reviewing the file with a text editor. If everything I require for my station is there, including <COMMENT:n>text, <TX_PWR:n>nnn or whatever, then and only then do I import to DXbase. Perhaps Jack and his gang or someone on the list could provide a complete ADIF list used ONLY by DXbase to help everyone out. There is some further information using ADIF files in the HELP files of DXbase. Good observation Dave, in short, you have been doing the import correctly and it is normally for some programmes not to export correctly or all the information you need. 73 Eric. -----Original Message----- From: Dave Chasey Hi All, I'm running DXBase 2006 and also use Writelog for contesting. After the NAQP I made an ADIF file from my Writelog log and imported it into DXBase, after making the appropriate backups of course. :-) I noticed that the state information from Writelog did not populate the State field in DXBase. Looking at the ADIF file created by Writelog, the state is actually labeled "QTH", not "STATE". If you try to import those records again after editing the ADIF file, DXBase rejects them since it would create a duplicate entry. In this case, I can easily restore the DXBase backup and import the edited log again. I also have previous QP logs though and I would like to "fix" them and transfer the state information from them to DXBase as well, so that wouldn't be an option for them. I know the LoTW import can update existing records with the new information, but if you try to use the LoTW import, it rejects it as not being a LoTW ADIF file. I can certainly look and see what differences there are between the Writelog and LoTW ADIF files and make it look the same, but I don't know if that import will fool with the "confirmed by LoTW" bit or not. I'll probably play with a 2 or 3 QSO "test" log and see what happens if I don't get a better idea. Has anyone else run into this issue? If so, is there an easier way to resolve it?
