Tom, It's a little hard to tell from your notes exactly what is or is not being included. Maybe a specific callsign example would help.
I use the DXCC function here and it seems OK in 2006. For the case you mention as QSLs you know should be listed but are not, a couple quick "reasons" come to mind: 1. The country (log column labeled prefix) of these "QSLs" has already been recognized by DXBase as being credited for DXCC. 2. The actual QSO you want does not indicate that a QSL has been received. There are several more possibilities as part of the selection logic etc but it sounds like you may have already addressed those. You can check item 1 above by running the report: Output / Standard Reports . Look in User Designed other DXCC Related list for the report dxcccredselect.rpt. If you run this report you will see everything DXBase "thinks" has been credited. Hope this helps but maybe a little more info from you could pin point the direction too. 73, George .. W1ZT At 07:17 PM 5/25/2005, TOM wrote: >IS anyone out there experiencing problems with the DXCC Worksheet report >for submission to ARRL as i am? i have spent about 3 weeks off and on >trying to get this report correct for field checking and have had numerous >problems getting it right? I havn't seen many posts on it except for >multiple q's which i figured out, but my problem is it listing q's already >credited and not listing ones that should be listed for submission? I have >gotten it down 2 two qsls i need to submit and have listed on report but >for some reason Dxbase 2006 will not recognize them not matter what i try >checking or unchecking in the awards field or select field? any help would >be appreciated here? one final note i have always done this by long hand >method up to know so this may be part of my problem but don't have a clue >how to correct it? TNX.....AA1BQ...TOM >______________________________________________________________ >Dxbase mailing list >Home: http://mailman.qth.net/mailman/listinfo/dxbase >Help: http://mailman.qth.net/mmfaq.htm >Post: mailto:[email protected]
