Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
IOTA Chasers: the IOTA tag for FK8HM in QRZ is incorrect
The IOTA tag displayed in QRZ's entry for FK8HM's is "EU-148 Languedoc-Roussillon Region group", but the LoTW confirmation I received for a QSO made earlier today specifies OC-032.
?
Neither the BigCTY nor the ClubLog exception lists include an entry for FK8HM; thus, I suggest manually adding an entry to DXView's Override List specifying that FK8HM is in OC-032.
?
? ? ? ?73,
? ? ? ? ? ?Dave, AA6YQ ? |
|
updated GridDXCC, eQSL AG, LoTW, and RDA databases are available ...
... via the Databases tab of DXView's Configuration window. Terminate DXKeeper, WinWarbler, and SpotCollector before directing DXView to update
these databases. ?
Because the GridDXCC database has been updated, you must also terminate and restart DXView after completing the update.
The GridDXCC database is what enables DXView to update it's Main window's "Location" box when you double-click in its World Map. This update of the Grid DXCC database by Joe W4TV improves the location information for 26 DXCC entities and U.S. States. Thanks Joe! ? ? 73,
? ? ? ? ? ? Dave, AA6YQ |
|
Re: SQL Filter
Thanks Joe. I set my dates as MM-DD-YYYY way back in 2007 and have always had it that way. It was an optional way to do the dates then and that is what I was used to. I don't know why that is not an option now, I just looked, but it was the way it was set up when I first started using it and those years. Also, the <> does work as NOT EQUAL. The first part of my expression work perfectly it was the last part that didn't work.
toggle quoted message
Show quoted text
73, Bob KB4CL -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV Sent: Sunday, April 20, 2025 2:08 PM To: [email protected] Subject: Re: [DXLab] SQL Filter 1) Your dates are incorrectly formatted ... should be YYYY-MM-DD 2) I'm not sure <> works for not equal ... Try the following: (mode='CW') AND (NOT DXCCPrefix = 'K') AND (QSO_Begin BETWEEN #2015-01-01# and #2024-12-31#) AND ((NOT APP_DXKEEPER_LOTW_QSL_RCVD = 'V') OR (NOT QSL_RCVD = 'V')) 73, ... Joe, W4TV On 2025-04-20 1:32 PM, Bob Main via groups.io wrote: It appears that I have worked a few DX stations in CW that I don't |
|
Re: SQL Filter
1) Your dates are incorrectly formatted ... should be YYYY-MM-DD
toggle quoted message
Show quoted text
2) I'm not sure <> works for not equal ... Try the following: (mode='CW') AND (NOT DXCCPrefix = 'K') AND (QSO_Begin BETWEEN #2015-01-01# and #2024-12-31#) AND ((NOT APP_DXKEEPER_LOTW_QSL_RCVD = 'V') OR (NOT QSL_RCVD = 'V')) 73, ... Joe, W4TV On 2025-04-20 1:32 PM, Bob Main via groups.io wrote:
It appears that I have worked a few DX stations in CW that I don't have |
|
Re: DXKeeper log not opening
+AA6YQ comments below
It is a back-up file which was made automatically on shut-down and saved to a flash drive. ?+ For whatever reason, Windows considers that file to be open. I suggest that you terminate all of your applications and reboot Windows. ? ? ?73, ? ? ? ? ? Dave, AA6YQ |
|
SQL Filter
¿ªÔÆÌåÓýIt appears that I have worked a few DX stations in CW that I don¡¯t have confirmed or verified.? I am attempting to write a SQL expression that searches for mode of CW and NOT a US QSO and it the QSO was between ?January 1, 2015 and January 1, 2025 (and that part works it is that last part of the expression that I can¡¯t get right).? Anway, this is what I have so far: ? (mode='CW') AND (DXCCPrefix <> 'K') AND ?((QSO_Begin > #01-01-2015 00:00#) AND (QSO_End < #01-01-2025 00:00#)) AND ((APP_DXKeeper_LotW_QSL_RCVD<>'V') OR (QSL_Rcvd <> 'V')) ? I don¡¯t get any errors.? I want it to now list only DX stations that have not been verified. ?I realized that is ¡°confirmation¡± but the ¡®V¡¯ appears in the LoTWR or QSLR columns.? Which explains why I have that part at the end. ?I looked at the Help (Log Items) at file:///C:/Ham%20Programs/DXLab/DXKeeper/Help/Items.htm and it shows an item App_DXKeeper_QSL_Verified but I couldn¡¯t figure out what to do with it since it appears one of its values is ¡®V¡¯, but when I tried it as a SQL expression I got an error.? What am I missing? ? 73, Bob KB4CL |
|
Re: DXKeeper log not opening
On 2025-04-20 12:31 PM, Jim Cary via groups.io wrote:
I get the message "attempt to open the log inE:\ZF2LC_2025-03-21_14-57-00.mdb failed" You are attempting to open a backup file created on 2025-03-21 14:57:00z The Microsoft Jet database stopped the process because you and another user are attempting to change the same data at the sameThat file is locked because it is open for writing by another instance of DXKeeper or another application. Are you specifying a log file on the DxLab Apps tab of DXLab Launcher or is the log specified in the Log File box in DXKeeper -> Config -> Log? Typically, the Log file is: ..\DXLab\DXKeeper\Databases\<call>.mdb 73, ... Joe, W4TV On 2025-04-20 12:31 PM, Jim Cary via groups.io wrote: I get the message "attempt to open the log in E:\ZF2LC_2025-03-21_14-57-00.mdb failed |
|
Re: Graphics cards and Monitors for the shack/ DXLab (about setting affinity)
About the application's affinity being transient. There is at least one way to set the affinity with DXLab Launcher. Here is the command line that I use to start WSJT-X in the Apps Started Before DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /C start /affinity 0x7 C:\Users\Public\wsjtx_2_7_0\bin\wsjtx.exe
?
This sets the affinity to processors 0, 1 and 2. The hex code 0x7 is a bit mask where LSB represents CPU0, the next bit CPU1 and so on. So for example for CPUs 2 and 3 you would use hex code 0x0C.
?
Here is how I start SpotCollector from the Apps Started After DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /K start /affinity 0x8 c:\Users\Public\DXLab\SpotCollector\SpotCollector.exe
?
I use the option /K, which leaves the window for cmd.exe running, beacuse otherwise I couldn't terminate SpotCollector with the Launcher. Termination method Close would need a static main window caption, which SpotCollector doesn't have and the kill method needs a running parent process (cmd.exe) for the Termination to work. So I choose the kill method in the Launchers Termination box.
?
I have of course disabled SpotCollector in the Launcher's DXLab Apps tab.
?
If I need to start SpotCollector manually I have to start it from the Apps Started After DXLab Apps tab's Start button, if I want to have the affinity set.
?
--
73 de Tapio at station OH3HN
?
?
On Sat, Apr 12, 2025 at 09:20 PM, Dave AA6YQ wrote:
?
?
? |
|
Re: Trouble with DXKeeper
+ AA6YQ comments below
Ok -- The problem is only with the US Contacts. QSO from Jan 1967 to Jun 1971 (12 QSO good) a close look at all the Broken ARRL Sections and those that were expanded for example older QSL with PA I have no problem, but my Section with WPA and EPA are listed as a Broken ARRL Section. Other rejected ARRL areas are WWA, STX, NNY, WCF, NFL, EB, SB, SJV, EMA,SCV,ORG, WNY, WTX, LAX, EMA, EWA, SDG.. It appears I have the Correct entries in the ARRL Section, but the program Checks the Section and is comparing it with and out dated List.. What file do I need to update?? + DXKeeper's Secondary Subdivision Database defines ARRL Sections smaller than a state. What is the modification date of the file SecondarySubdivisonDatabase.mdb + In DXKeeper's Databases folder? + The correct date is 2025-01-14. + A self-extracting executable containing SecondarySubdivisonDatabase.mdb + is available via 73, Dave, AA6YQ |
|
Re: Trouble with DXKeeper
Ok --
The problem is only with the US Contacts.
QSO from Jan 1967 to Jun 1971 (12 QSO good)
?
a close look at all the Broken ARRL Sections and those that were expanded for example older QSL with
PA I have no problem, but my Section with WPA and EPA are listed as a Broken ARRL Section. Other rejected
ARRL areas are WWA, STX, NNY, WCF, NFL, EB, SB, SJV, EMA,SCV,ORG, WNY, WTX, LAX, EMA, EWA, SDG..
?
It appears I have the Correct? entries in the ARRL Section, but the program Checks the Section and is comparing
it? with and out dated List..? What file do I need to update??
Thanks? Dan? KX7Dx
?
? |
|
Re: Trouble with DXKeeper
I did a restore from my backup before the duplicate file removal and no change.. It appears all the incorrect information for the Contact is in the "Award Panel".. what Award txt is the information for a QSO stored in??
+ All QSO information - including the information displayed in items in the Award panel on the Main window's "Log QSO" tab - is stored in your log. + What's an example of a QSO whose displayed information is incorrect? 73, Dave, AA6YQ |
|
Re: Trouble with DXKeeper
+ AA6YQ comments below
I did a clean up duplicate files on my DXLab computer and removed a lot of the DX Lab files. + The only files that should be removed are old versions of DXLab applications and old versions of DXView databases.
I reinstalled the DXLab Suite and then+ That's the automotive equivalent of pulling your car's engine after you cleaned all the junk out of its trunk. No benefit, but lots of risk. but not every thing has come back.+ That' why I strongly and repeatedly advise users to never uninstall and re-install DXLab applications unless there is hard evidence that the installation has become corrupt, e.g. messages of the form "Component X is missing" or "Library Y cannot be found". ?
+ At this point, the state of DXLab on your system is "unknown". When I run a Recompute Actions report -- All my qso are listed as the "Broken: ARRL Section ___ is inconsistent with DXCC Entity K and State ___ and County ___,______ . I checked and all the US States have been changed as well as the County.. It appears Call, Date, band. Mode, DXCC ID (all 291) DXCC (All United States. I having another problem, but I will submit it after I get this resolved. + Make a copy of the log backup you created before you started the cleanup process and revert to this copy of your log. ? ? ?73, ? ? ? ? ? ?Dave, AA6YQ |
|
Re: WAC report
+ AA6YQ comments below
+ A QSO's Continent item can be set in several ways, depending upon how you had DXKeeper configured at the time: by your directly specifying it, from a callbook lookup, from an override, or from a previously-logged QSO with the same callsign. + Did you originally log the QSO with DXKeeper in 2014? ?
? ? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
|
Trouble with DXKeeper
I did a clean up duplicate files on my DXLab computer and removed a lot of the DX Lab files.. I reinstalled the DXLab Suite and then
did a update, but not every thing has come back. When I run a Recompute Actions report -- All my qso are listed as the "Broken: ARRL Section ___ is inconsistent with DXCC Entity K and State ___ and County ___,______ . I checked and all the US States have been changed as well as the County.. It appears Call, Date, band. Mode, DXCC ID (all 291) DXCC (All United States. I having another problem, but I will submit it after I get this resolved.. Thanks Dan KX7DX |
to navigate to use esc to dismiss