If your log consists of multiple call signs as mine does, for instance. WN9VOL then it continues on the date of new license to WA9VOL, which runs to new vanity call license date. >From there on it's W9OL Each section of my log shows the proper Oper Call for that time frame. No problemo
So if you download all, taking all qsls from any of these callsigns, the import will mark those that are qsled. If you then repeated the import, it would not overwrite the LoTW received date. It will not add a extraneous qso into the log. If ...you had uploaded a log from a contest that you used Writelog (for example), but did not import that writelog file into DXBase AND you received qsls for those writelog qsos THEN DXBase would see those qsls as qso's that SHOULD be entered into your DXBase log and will so include them. You will still be missing the qso's from the writelog file that have not be qsled as yet. that is why I contest on weekends, import my contest log into DXBase and then select all as yet not exported to LotW qsos. That file is then signed and uploaded to LoTW... Which to me is a logical succession. Hope I answered your questions for you ----- Original Message ----- From: "Earl" <[EMAIL PROTECTED]> To: "FireBrick" <[EMAIL PROTECTED]> Sent: Friday, March 24, 2006 9:07 AM Subject: Re: [Dxbase] Importing LoTW ADIF for 2 calls > Bill, > > I have a question about importing from LoTW. I guess I have not payed any > attention > about the operator call box on the import templete. > > Question is if I download all my LoTW QSL's for just my old call (KD5ZM) and > import them > into DXB will it mess up the log if they are already shown as confirmed? I > guess what I > am saying is will a duplicate imported confirmation mess up the log? That is > if they are > already shown as confirmed. > > Hope I made myself clear. > > Thanks, Earl N5ZM.. > > PS. I'm still having trouble with Writelog/MMTTY/microKEYER. I will try to > set up F-Keys > next week. So I may contact you with some questions about that and switching > from CW to > RTTY and getting the Blue Screen. I think it has something to do with the > comm7 > assignment by MK. When I try to go to CW it tells me comm7 not available. > ----------------------- > > > > FireBrick wrote: > >> One addendum to the previous explanation about importing from LoTW. >> >> The next time you open Non-DXBase Import module, the callsign will revert to >> the >> default call of your registered program/log. >> So you will have to remember to remove unwanted callsigns and change to the >> callsign of >> the qso's you only want to download. >> >> >> >> >> >> >> >> ----- Original Message ----- From: "FireBrick" <[EMAIL PROTECTED]> >> To: <[email protected]>; "Peter W2IRT" <[EMAIL PROTECTED]> >> Sent: Friday, March 24, 2006 5:51 AM >> Subject: Re: [Dxbase] Importing LoTW ADIF for 2 calls >> >> >>> I think the error is because you did not select which callsign you wanted >>> during the >>> import procedure. >>> >>> First, when I download, I only select a particular callsign to be >>> downloaded. >>> >>> and second, when you do the actual 'non-dxb import', you should always >>> select which >>> callsigns qsos you want. >>> Sort of a double check. >>> >>> In the import screen, you will see QSOs for these OPR Calls >>> Usually just one call, the default call the program is registered to. >>> If I'm importing qso's for my older calls, I delete W9OL and type in WA9VOL >>> I then enter WA9VOL into the field Default Opr Call if not in source data. >>> (that's really only necessary if importing from some other program which >>> may not have >>> a Operator Call field) >>> >>> This way, if a qso for one of the stations I manage, and obviously was >>> under my basic >>> certificate was included in the download, it will be skipped and not added >>> to my W9OL >>> log. >>> >>> You may ask why that's even necessary. >>> Well I manage a number of callsigns. I don't want to download 11 separate >>> lotwdownload.adi files >>> So I just download them all in one >>> Then I do a import and select the target database. >>> Say 9x5aa and make sure that only 9x5aa is in that QSOs for these OPR Calls >>> field >>> do the import and only 9x5aa Lotw data will be imported. >>> then I can move on to the next managed callsign and it's target .mdb file >>> change that call in that filed, rerun the import, and it will select and >>> import only >>> the changed callsigns qso/qsls. >>> >>> So it's not so much what you chose to 'download'. >>> It's more a choice of what you chose to 'import'. >>> >>> Hope this helps. >>> I learned this the hard way also. >>> But.... >>> As I do a safety backup before any import...I was able to revert back and >>> redo the >>> import correctly. >>> >>> BACKUP, BACKUP, BACKUP! >>> >>> >>> >>> >>> >>> ----- Original Message ----- From: "Peter W2IRT" <[EMAIL PROTECTED]> >>> To: <[email protected]> >>> Sent: Thursday, March 23, 2006 11:48 PM >>> Subject: [Dxbase] Importing LoTW ADIF for 2 calls >>> >>> >>>> Hi All, >>>> >>>> Just ran into an interesting snag with an LoTW import. I imported a LoTW >>>> ADIF into my >>>> /C6A log and it added QSOs from my regular W2IRT log to the separate /C6A >>>> log. Why is >>>> this happening, and what can I do to prevent it in future? Without >>>> looking, I'll bet >>>> the reverse happened too, so now I have to go in and delete a slew of bad >>>> Q's from >>>> there too. >>>> >>>> >>>> >>>> - Peter >>>> >>>> W2IRT >>>> >>>> ______________________________________________________________ >>>> 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] >> > > -- > Earl F. Smith - N5ZM > PO Box 20065 > White Hall, AR 71612-0065 > >
