Jack, all, Still some troubles on the frontline ;-) I ran the filters trough the selection wizard but (only for test) get more then 1200 records for labeling. I only made 200 QSO's last month so th so I think some logbook flags are not imported well.
I will use the selection filter based on date to select the qso's for labeling to get them printed today. Now after that i like to set ALL my logbook entries to QSL SENT so the next time only new inputted log items wil be set for printing labels. SO how can I proceed making this happen, that my complete logbook is set to labels printed and QSL is sent. And will my new entries be automaticly set for QSL labling or not, how to set this items. I find the learning curve rather steep but this because the program will offer a lot I guess. Thanks all a lot for helping out. Phil ON4VP (dxbase newbie) ----- Original Message ----- From: "Jack" <[EMAIL PROTECTED]> To: "Phil ON4VP" <[EMAIL PROTECTED]> Sent: Wednesday, November 06, 2002 12:04 AM Subject: Re: [DXBase] import problems > Hi Phil, > > Glad to hear that we are making progress.. hihi.... > > If I understand correctly, you now have QSL sent fields marked correctly > from the ADIF import. And, now you wish to print labels for any QSOs where > the QSL Sent field is not turned on? If this understanding is correct, then > the following would probably do what you want. > > 1. Select from the main DXbase menu Tools | Selection Wizard. > 2. On the Selection Wizard screen, select output = Label from drop down > list. > 3. Remove the check from Test Only. > 4. Click QSO Filter button. > 5. Click No QSL Sent. Maybe you also want Not confirmed ? Not sure. > There are other filters you will see that you might want to use. I leave > that to you. > 6. Click OK on QSO Filter screen after selecting your choices. > 7. Click Start on the main Wizard screen. > > This will create a QSO label for each QSO that meets the filter criteria > that you selected. It does not print labels at this point, only stores the > label info into a pending file for printing later. > > To View your pending QSO labels: > 1. From DXbase menu, select Tools | Database Access | Labels > 2. On next screen that appears, click QSO tab to see QSO labels. > 3. I will assume 1 QSO per label so we leave that alone. > > To Print your pending QSO lables: > 1. From DXbase menu, select Output | User Designed Labels. > 2. On next window, select QSO Labels. > 3. On next screen, select 5160-1q.lbl ( this would be a label design using > 1 QSO per label on a 5160 type label ) > 4. Click Open. > 5. To print to printer, select the printer, to view on screen select > Preview, etc... from the box with down arrow. > > I hope this gets you started on labels quickly. There is a lot of > additional flexibility and many other things to learn about label process in > DXbase. It is far more powerful than most other programs. We suggest that > you review the help file in detail to learn more about it. By the way, we > have other customers in Belgium who have done their own label and QSL card > designs. > > Hope this helps, > Jack > > PS We recommend that you post your questions to the DXbase Reflector where > others can offer their advice about how to do things too. We have many > experts... hihi... > ----- Original Message ----- > From: "Phil ON4VP" <[EMAIL PROTECTED]> > To: "Jack" <[EMAIL PROTECTED]> > Sent: Tuesday, November 05, 2002 3:55 PM > Subject: Re: [DXBase] import problems > > > > Jack, > > > > I'm almost in buisness. I have a new log into a fresh installed program. > > I updated counties, I installed import.exe 1.01. > > > > I now had only 53 errors due to bad data in adif. > > (I can live with this and will correct manually). > > > > I have QSL sent flags marked 'on' now. > > > > > > Now for a quick result, because QSL day at local club is on friday. > > If I want to print out all the QSO's on labels that not yet have been > sent. > > > > How do I proceed, makes the program its own filter for this. > > Wil flags be set auto to 'sent' after printen, etc ... > > > > Pse can you help me gettings started, thank you. > > > > If I check status of awards, is it only showed by 'confirmed' or can I for > > example check how many countries I've worked ... ? > > > > Thank you very much, > > Phil ON4VP > > > > ----- Original Message ----- > > From: "Jack" <[EMAIL PROTECTED]> > > To: "Phil ON4VP" <[EMAIL PROTECTED]> > > Sent: Tuesday, November 05, 2002 9:30 PM > > Subject: Re: [DXBase] import problems > > > > > > > OK, let's regroup. On the support page of our web site, you will find a > > > link to where you can download an updated version of the import utility. > > > Just download this and apply per the instructions on our web and this > will > > > take care of the problem with the Zero length field. > > > > > > Also, on our web support page you will see a link to five or six US > county > > > name changes. Print this out so you will have it to refer to later. > > > > > > Now, I'm not sure what your current situation might be. Since you > already > > > attempted the import and have some QSOs already imported, it is probably > > > best to just start over with a clean install and an empty database. So, > > > let's try this approach: > > > > > > 1. Using control panel, uninstall DXbase in its entirety. > > > 2. Using Windows Explorer, delete the DXbase 2003 folder under Program > > > Files, Scientific Solutions and all that is in it. > > > 3. Using Windows Explorer, delete the DXB2003.INI file located in your > > > Windows folder. > > > > > > This gets you a clean slate. > > > > > > Now, > > > > > > 1. Install DXbase 2003 accepting the defaults. > > > 2. Download the import patch from the web and apply that per the > > > instructions on the web. > > > 3. Open DXbase 2003 and choose Tools | Database Access | US States and > > > Counties. Using the paper you printed from above, make the name changes > > to > > > the US County names that are listed on the paper. > > > > > > This gets DXbase 2003 as current as it can be. > > > > > > Now, we are ready to do the .adi import again. You might want to look > at > > a > > > few of the entries in your .adi where you were seeing the problem with > SSB > > > and 599. My guess is that this is being exported this way by DX4WIN. > > > > > > Anyway, let's try the above approach and see how we do. If you need any > > > further guidance, please let us know. We want to try and help you make > > the > > > transition as easily as we can. > > > > > > Regards, > > > Jack > > > > > > ----- Original Message ----- > > > From: "Phil ON4VP" <[EMAIL PROTECTED]> > > > To: "Jack" <[EMAIL PROTECTED]> > > > Sent: Tuesday, November 05, 2002 3:24 PM > > > Subject: Re: [DXBase] import problems > > > > > > > > > > Jack, > > > > > > > > Yes, I got many 'zero lenght' errors indeed. > > > > I don't know to what they reflect. > > > > > > > > I exported my log from dx4win 503 to ADIF > > > > a few hundred qso's where not imported due to that error but also > > because > > > of > > > > report with 3 caracters (599) instaed of two for SSB modes. This is > > > trange > > > > to. > > > > > > > > Regards, Phil ON4VP > > > > > > > > ----- Original Message ----- > > > > From: "Jack" <[EMAIL PROTECTED]> > > > > To: "Phil ON4VP" <[EMAIL PROTECTED]>; <[email protected]> > > > > Sent: Tuesday, November 05, 2002 9:09 PM > > > > Subject: Re: [DXBase] import problems > > > > > > > > > > > > > Phil, > > > > > > > > > > We are not aware of any errors in the DXbase ADIF import process. > My > > > > > feeling is that when errors are reported, they are caused by invalid > > > data > > > > in > > > > > your .ADI file exported from some other program. Also, if some > fields > > > are > > > > > not populated such as the one you mention, it is most likely because > > > that > > > > > field is not contained in your .adi file. You can see what is in > your > > > > .adi > > > > > file by opening it with notepad or wordpad. If you would like to > > email > > > me > > > > > your .adi file, I will be happy to take a look and give you a more > > > precise > > > > > explanation. If it is found that DXbase has some error, we will of > > > course > > > > > correct it; however, if the data in the .adi file is inaccurate or > > > > > incomplete, this would be beyond our control. > > > > > > > > > > Please be aware that we did post an updated import utility that > > corrects > > > a > > > > > specific issue with a zero length error being reported but I don't > > think > > > > you > > > > > are experiencing this. Also, we did post a few US county name > changes > > > on > > > > > our web site that you can make to your county database in case some > of > > > > these > > > > > are the ones you were having some difficulty with. > > > > > > > > > > Please send your .adi file to > > > > > > > > > > [EMAIL PROTECTED] > > > > > > > > > > Regards, > > > > > Courtney > > > > > > > > > > ----- Original Message ----- > > > > > From: "Phil ON4VP" <[EMAIL PROTECTED]> > > > > > To: <[email protected]> > > > > > Sent: Tuesday, November 05, 2002 2:58 PM > > > > > Subject: [DXBase] import problems > > > > > > > > > > > > > > > > Hi to all, > > > > > > > > > > > > I just received my cdrom with DXbase 2003 today. > > > > > > I installed it on Win XP Pro. > > > > > > > > > > > > I tried to import my ADIF logs that I have prepared out of DX4win > > 503. > > > > > > I had enormous errors and many, many logs are not written into my > > new > > > > > > database file. > > > > > > > > > > > > I had also all my qsl flags destroyed so I do not know anymore > where > > I > > > > > sent > > > > > > my cards to. > > > > > > > > > > > > So my first impression is not as good as I hoped. > > > > > > I don't know where to start now to set things straight. > > > > > > > > > > > > First it will take me an enormous amount of time to check wheter a > > QSL > > > > was > > > > > > sent or not since my flags are gone. > > > > > > I also have a few hundred of QSO not imported, I can' t understand > > why > > > > > > DXbase tells me errors are encountered. > > > > > > I check and while imprting, lot's of QSO in SSB are set to 599 > > reports > > > > and > > > > > > errors occure, but they where exported and checkd as 59 reoports. > > > > > > > > > > > > Also several counties are not recognised. > > > > > > > > > > > > > > > > > > Anyhow, after spending 99 bucks I will have to do a lot of manual > > > work. > > > > > > So far for ADIF compatibility and importing. > > > > > > > > > > > > I have several questions for manual processing the imported qso's > : > > > > > > > > > > > > 1) How does one look up a previous QSO (f.e. to confirm a qsl card > > > > > received) > > > > > > 2) where can I check QSL statusses ? > > > > > > 3) can I select f.e. 300 QSO's in one time and set the flags as > > 'sent' > > > > so > > > > > > when I start putting new SQO's in, I have them check for printing > > > labels > > > > > and > > > > > > not all the imported where the flags are gone. > > > > > > > > > > > > Thanks for any help offered. > > > > > > Phil ON4VP > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > > To UNSUBSCRIBE please visit: > > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > To UNSUBSCRIBE please visit: > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
