Date   

Re: DXLab Restore Problem

Alan Swinger
 


Dave - apparently I am doing something wrong w/ the Workspace. When I select Folder in the Workspace box and click Load Settings I get a Registry Editor Box with a question: Do you want to allow this app to make changes to your device? Whether I click Yes or No, the Box does not go away.
I tried to create a new Workspace from my Laptop DXLab system, get the same result.
I compared contents of the PF files on the laptop (working OK) w/ the DT we are working on and the only File Folder missing on the latter is the INSTALL file. Is it possible to simply copy it to a thumb drive and put into the PF folder on the DT? 
The Script Error that pops uo says:
Script Error with a message that says an error has occurred in the script on this page and the shows:
Line   0
Char   0
Error   Script Error
Code   0
URL: https://pagead2.googlesyndication.com/pagead/show_ad.js

Re the instructions you gave me to fix the DXLab App paths in the Launched Config window, the executable files I selected were the latest version of the several that showed in each of the Explorer DXLab app files  . .  in which the .exe is not shown. In the updated Launcher Config list, the .exe is shown after each. I assume that when the inevitable updates come, these will all update OK. Sent a screen shot of the Launcher Config list to you separately so yuou can see what I am saying.
Thanks - Alan K9MBQ 


-----Original Message-----
>From: Dave AA6YQ
>Sent: Sep 14, 2020 9:45 PM
>To: DXLab@groups.io
>Subject: Re: [DXLab] DXLab Restore Problem
>
>+ AA6YQ comments below
>
>Also, in PF, the only one of the 12 Search Buttons populated is QRZ - the rest are blank. On my Laptop, they are all populated. What do I need to do?
>
>+ Terminate Pathfinder, direct the Launcher to restore Pathfinder's settings from your saved Workspace, and then start Pathfinder.
>
>Also, keep getting a Script running error message on both machines??
>
>+ What is a "Script running error message"?
>
>Pls advise.
>
>+ Never allow the staff of a store to modify your computer.
>
> 73,
>
> Dave, AA6YQ
>
>
>
>
>
>


Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Also, in PF, the only one of the 12 Search Buttons populated is QRZ - the rest are blank. On my Laptop, they are all populated. What do I need to do?

+ Terminate Pathfinder, direct the Launcher to restore Pathfinder's settings from your saved Workspace, and then start Pathfinder.

Also, keep getting a Script running error message on both machines??

+ What is a "Script running error message"?

Pls advise.

+ Never allow the staff of a store to modify your computer.

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Alan Swinger
 

Dave - Roger, and those actions got SC going . .. . there was no Spots file in the database file, so put the spots mdb into it as suggested, so have an empty Spots.mdb now.

Also, in PF, the only one of the 12 Search Buttons populated is QRZ - the rest are blank. On my Laptop, they are all populated. What do I need to do? Also, keep getting a Script running error message on both machines??
Pls advise.
Tks - Alan K9MBQ

-----Original Message-----
From: Dave AA6YQ <@AA6YQ>
Sent: Sep 14, 2020 6:06 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab Restore Problem

+ AA6YQ comments below

Dave - That action seems to have solved the Launcher link to all the apps except Spot Collector. When opening via Launcher, I get a "does not exist" message for C:\ProgramFiles\DXLabSuite\SpotCollector\Databases\Spots.mdb . . . which is where we were before . . . AND the Config Spot Database File address is C:\Program Files\DXLab Suite\SpotCollector\Databases\Spots.mdb.

Seems like this also needs to be changed to a DXLab address!?

+ Correct. In the "Spot Datbase File" panel at the top of the "Spot Database" tab of SpotCollector's Configuration window, click the Select button, and then use the Open window to navigate to

C:\DXLab\SpotCollector\Databases

+ and select the file Spots.mdb (assuming one is present)

+ If there's no Spots.mdb file in your

C:\DXLab\SpotCollector\Databases

+ then just past

C:\DXLab\SpotCollector\Databases\Spots.mdb

+ into the "Spot Database File" panel's pathname box. Terminated SpotCollector, and restart it; an empty new Spots.mdb will be created.

73,

Dave, AA6YQ





Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave - That action seems to have solved the Launcher link to all the apps except Spot Collector. When opening via Launcher, I get a "does not exist" message for C:\ProgramFiles\DXLabSuite\SpotCollector\Databases\Spots.mdb . . . which is where we were before . . . AND the Config Spot Database File address is C:\Program Files\DXLab Suite\SpotCollector\Databases\Spots.mdb.

Seems like this also needs to be changed to a DXLab address!?

+ Correct. In the "Spot Datbase File" panel at the top of the "Spot Database" tab of SpotCollector's Configuration window, click the Select button, and then use the Open window to navigate to

C:\DXLab\SpotCollector\Databases

+ and select the file Spots.mdb (assuming one is present)

+ If there's no Spots.mdb file in your

C:\DXLab\SpotCollector\Databases

+ then just past

C:\DXLab\SpotCollector\Databases\Spots.mdb

+ into the "Spot Database File" panel's pathname box. Terminated SpotCollector, and restart it; an empty new Spots.mdb will be created.

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Alan Swinger
 

Dave - That action seems to have solved  the Launcher link to all the apps except Spot Collector. When opening via Launcher, I get  a "does not exist" message for C:\ProgramFiles\DXLabSuite\SpotCollector\Databases\Spots.mdb . . . which is where we were before . . . AND the Config Spot Database File address is C:\Program Files\DXLab Suite\SpotCollector\Databases\Spots.mdb.
Seems like this also needs to be changed to a DXLab address!? Thoughts?

Re what else needs to be fixed . . ., not sure yet until I chk all workspace parameters, but looks good so far!! 
Tks for all the time, effort and tutoring  - much appreciated. - Alan K9MBQ

P.S. Last Item: Seems like this also needs to be changed to a DXLab address!? Thoughts?


On Mon, Sep 14, 2020 at 11:43 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Dave- Commander and all DXLab apps are in  C:\DXLab folder, incl Launcher which opens from there.

+ The screen shot you sent me shows that the Launcher thinks that all of your other DXLab applications are installed in C:\Program Files. That is why the Launcher cannot start your other DXLab applications.

+ To correct this, select the "DXLab Applications" tag on the Launcher's Configuration window, and for each DXLab application other than the Launcher, click its Sel button; in the "Open" window that appears, navigate to the folder in C:\DXLab that contains the application, and select the application's executable file, e.g.

CI-V Commander.exe

+ After you complete this, the Launcher should be able to start your DXLab applications.

+ What else isn't working?

          73,

                 Dave,. AA6YQ







Re: error when updating log

Dave AA6YQ
 

+ AA6YQ comments below

so With no other software updating dxkeeper (JTAlert closed) i was not able to update the log from the QSL tab. As before there was a popup window that 'blinked' but nothing else happened

+ Robert, this thread began with you stating that you'd printed QSL cards and updated your log to reflect that printing, but had forgotten to print address labels:

<https://groups.io/g/DXLab/message/196249>

+ I explained how to filter the Log Page Display to contain the QSOs for which you printed QSL cards and load those QSOs into the QSL Queue so you could print address labels; I assume that this's complete.

+ You now seem to expect that running the "Update Log" function will update your log and clear the QSL Queue. That's not the case. QSL cards have already been generated from the QSOs now present in the QSL queue, and your log has already been updated to reflect that fact. To clear the QSL Queue, click the Clear button on the Main window's QSL tab.

73,

Dave, AA6YQ


Re: TQSL issue

Dave AA6YQ
 

+ AA6YQ comments below

Gm all. I was doing my QSL'ing from the VHF contest this weekend this morning and a note popped up that a new ver of TQSL was available, so I tried to update. During the install I got a missing or corrupted CAB1.CAB file. I went to find the file and delete and start over and the TQSL folder and files are no longer on my machine and it will not let me do a clean install. I get the same error. Attached is the errorlog from this morning.

+ An errorlog generated by a DXLab application would not be helpful in debugging a TQSL installation problem; also, attachments are not conveyed by this group.

+ For problems with TQSL, either send email to

LoTW-help (at) arrl.org

+ or post a message on the ARRL-LoTW group, which everyone is welcome to join:

<https://groups.arrl.org/g/ARRL-LoTW/messages>

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave- Commander and all DXLab apps are in C:\DXLab folder, incl Launcher which opens from there.

+ The screen shot you sent me shows that the Launcher thinks that all of your other DXLab applications are installed in C:\Program Files. That is why the Launcher cannot start your other DXLab applications.

+ To correct this, select the "DXLab Applications" tag on the Launcher's Configuration window, and for each DXLab application other than the Launcher, click its Sel button; in the "Open" window that appears, navigate to the folder in C:\DXLab that contains the application, and select the application's executable file, e.g.

CI-V Commander.exe

+ After you complete this, the Launcher should be able to start your DXLab applications.

+ What else isn't working?

73,

Dave,. AA6YQ


Re: error when updating log

Robert galambos
 

so With no other software updating dxkeeper (JTAlert closed) i was not able to update the log from the QSL tab. As before there was a popup window that 'blinked' but nothing else happened


2020-09-14 13:43:08.020 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 1, ColIndex = 10
2020-09-14 13:43:08.025 >    theColName = QSL_VIA
2020-09-14 13:43:08.026 >    DXLogSetup.TooltipsCheckbox.Value = 1
2020-09-14 13:43:08.039 >    Callsign = KF7OKJ, CellContents =
2020-09-14 13:43:08.040 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip
2020-09-14 13:43:12.925 > DXLogMain.TabbedDialog_Click 1, PreviousTab = 0
2020-09-14 13:43:12.928 > DXLogMain.TabbedDialog_Click: saved Main LogTab window height = 13935, width = 27300
2020-09-14 13:43:12.929 > DXLogMain.SelectTab: 1
2020-09-14 13:43:13.015 > GetstringSetting,  Section = Windows, Key = MainQSLHeight, Result = 14340
2020-09-14 13:43:13.021 > DXLogMain.Form_Resize: Resize ignored
2020-09-14 13:43:13.024 > GetstringSetting,  Section = Windows, Key = MainQSLWidth, Result = 28800
2020-09-14 13:43:13.033 > DXLogMain.Form_Resize: Resize ignored
2020-09-14 13:43:13.061 > DXLogMain.Form_Resize start, tab = 1, windowstate = 0, top = 600, left = 0, height = 14340, width = 28800
2020-09-14 13:43:13.154 > DXLogSetup.UpdateQSLKeyVisibility
2020-09-14 13:43:13.155 >    MainDualColumns not checked
2020-09-14 13:43:13.156 > DXLogMain.Form_Resize complete, height = 14340, width = 28800
2020-09-14 13:43:13.157 > DXLogMain.SelectTab: Main QSLTab window height = 14340, width = 28800
2020-09-14 13:43:13.158 > DXLogMain.Form_Resize start, tab = 1, windowstate = 0, top = 600, left = 0, height = 14340, width = 28800
2020-09-14 13:43:13.160 > DXLogSetup.UpdateQSLKeyVisibility
2020-09-14 13:43:13.162 >    MainDualColumns not checked
2020-09-14 13:43:13.163 > DXLogMain.Form_Resize complete, height = 14340, width = 28800
2020-09-14 13:43:16.881 > DXLogMain.ValidFields: KB2ELA
2020-09-14 13:43:16.886 > DXLogMain.ValidFields: complete
2020-09-14 13:43:16.887 > DXQSLModule.ProcessPrintedQSLs: start, CurrentQSLMode = 1, QSL Queue RecordCount = 1
2020-09-14 13:43:16.888 > DXLogMain.ValidFields: KB2ELA
2020-09-14 13:43:16.892 > DXLogMain.ValidFields: complete
2020-09-14 13:43:16.930 > WAZModule.UpdateWAZDetailGrid
2020-09-14 13:43:16.947 > WAZModule.UpdateWAZDetailGrid: CQ Zone 5
2020-09-14 13:43:16.952 > WAZModule.UpdateWAZDetailGrid: complete
2020-09-14 13:43:16.954 > RecomputeWASStateProgress, State = mi, eQSLVUCC = False
2020-09-14 13:43:16.988 > WASModule.UpdateWASProgress: Call = N8SHZ, thePropMode =
2020-09-14 13:43:16.989 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:16.990 > WASModule.UpdateWASProgress: Call = N8SHZ, thePropMode =
2020-09-14 13:43:16.992 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:16.994 > WASModule.UpdateWASProgress: Call = EU1A, thePropMode =
2020-09-14 13:43:16.996 > WASModule.UpdateWASProgress: complete (no change)
2020-09-14 13:43:16.998 > WASModule.UpdateWASProgress: Call = NF8J, thePropMode =
2020-09-14 13:43:16.999 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.000 > WASModule.UpdateWASProgress: Call = KB8SRX, thePropMode =
2020-09-14 13:43:17.002 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.003 > WASModule.UpdateWASProgress: Call = N8YBL, thePropMode =
2020-09-14 13:43:17.005 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.006 > WASModule.UpdateWASProgress: Call = WB8BIL, thePropMode =
2020-09-14 13:43:17.007 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.009 > WASModule.UpdateWASProgress: Call = KB8ZGL, thePropMode =
2020-09-14 13:43:17.011 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.012 > WASModule.UpdateWASProgress: Call = W8LLL, thePropMode =
2020-09-14 13:43:17.014 > WASModule.UpdateWASProgress: complete
2020-09-14 13:43:17.015 > WASModule.UpdateWASProgress: Call = K8DID, thePropMode =
2020-09-14 13:43:17.016 > WASModule.UpdateWASProgress: complete (no change)
2020-09-14 13:43:17.033 > RecomputeWASStateProgress: complete
2020-09-14 13:43:17.035 > DXLogModule.FilterDisplay: start, Filter =
2020-09-14 13:43:17.037 > DXLogModule.FilterDisplay, theCriteria = (Call = 'KB2ELA') and (QSO_Begin = #2020-09-13 21:45:00#)
2020-09-14 13:43:17.130 > DXLogMain.LogPosition_Reposition: ignored
2020-09-14 13:43:17.131 > DXLogModule.FormatLogGrid: start
2020-09-14 13:43:19.243 > DXLogModule.RestoreHorizontalScroll
2020-09-14 13:43:19.632 >    CurrentLeftCol =
2020-09-14 13:43:19.633 > DXLogModule.FormatLogGrid: complete
2020-09-14 13:43:19.634 > DXLogModule.FilterDisplay: select QSO
2020-09-14 13:43:19.674 > DXLogMain.LogPosition_Reposition: RepositionCallsign = KB2ELA, RepositionAbsolute = 1365
2020-09-14 13:43:19.675 > DXLogMain.LogPosition_Reposition: disabling CallbookCmd
2020-09-14 13:43:19.678 > DXLogMain.LogPosition_Reposition: complete
2020-09-14 13:43:19.681 > DXLogModule.FilterDisplay: Selected KB2ELA @ 2020-09-13 9:45:00 PM
2020-09-14 13:43:19.685 > DDEClientModule.DXViewUpdateLogFilter ignored -- DXView not connected
2020-09-14 13:43:19.687 > DXLogMain.ValidFields: KB2ELA
2020-09-14 13:43:19.690 > DXLogMain.ValidFields: complete
2020-09-14 13:43:19.693 > DXLogModule.FilterDisplay: complete
2020-09-14 13:43:19.694 > DXLogModule.UpdateDetailGrid
2020-09-14 13:43:19.697 > DXLogModule.UpdateDetailGrid: K
2020-09-14 13:43:19.702 > StatusString.UpdateGrid
2020-09-14 13:43:19.705 > StatusString.UpdateGrid complete
2020-09-14 13:43:19.706 > DXLogModule.UpdateDetailGrid: complete
2020-09-14 13:43:19.707 > GetstringSetting,  Section = General, Key = CurrentDXCCID, Result =
2020-09-14 13:43:19.709 > DXQSLModule.ProcessPrintedQSLs: complete, CurrentQSLMode = 1, QSL Queue RecordCount = 1
2020-09-14 13:43:19.934 > DXLogMain.RowChangeLookupTimer_Timer
2020-09-14 13:43:19.937 > DXLogModule.UpdateFieldVisibility, DXCCID = 291
2020-09-14 13:43:19.939 > DXLogModule.UpdateFieldVisibility: unneeded
2020-09-14 13:43:19.940 > DXLogMain.ValidFields: KB2ELA
2020-09-14 13:43:19.943 > DXLogMain.ValidFields: complete
2020-09-14 13:43:19.944 > DXLogModule.UpdateProgressDisplays
2020-09-14 13:43:19.946 > DXLogModule.UpdateDetailGrid
2020-09-14 13:43:19.949 > DXLogModule.UpdateDetailGrid: K
2020-09-14 13:43:19.954 > StatusString.UpdateGrid
2020-09-14 13:43:19.956 > StatusString.UpdateGrid complete
2020-09-14 13:43:19.958 > DXLogModule.UpdateDetailGrid: complete
2020-09-14 13:43:19.959 > WAZModule.UpdateWAZDetailGrid
2020-09-14 13:43:19.962 > WAZModule.UpdateWAZDetailGrid: CQ Zone 5
2020-09-14 13:43:19.968 > WAZModule.UpdateWAZDetailGrid: complete
2020-09-14 13:43:19.971 > DXLogMain.RowChangeLookup (not suppressed) KB2ELA
2020-09-14 13:43:19.972 > DDEClientModule.PrefixLookup, theCallsign = KB2ELA, theDXCCPrefix = K
2020-09-14 13:43:19.973 > DDEClientModule.PrefixLookup invoking DXLogModule.LookupByPrefix because DXView is not running
2020-09-14 13:43:19.974 > DXLogModule.LookupByPrefix, thePrefix = K
2020-09-14 13:43:19.977 > DDEClientModule.PrefixLookup, LotW = , eQSL =
2020-09-14 13:43:19.978 > DDEClientModule.UpdateLatLon: 26 30' 0" N, 81 0' 0" W ignored -- DXView not connected
2020-09-14 13:43:19.980 > DXLogMain.RowChangeLookupTimer_Timer: enabling CallbookCmd
2020-09-14 13:43:19.981 > DXLogMain.RowChangeLookupTimer_Timer: complete


Re: DXLab Restore Problem

Alan Swinger
 

Dave- Commander and all DXLab apps are in  C:\DXLab folder, incl Launcher which opens from there. - Alan K9MBQ


On Sun, Sep 13, 2020 at 8:48 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Dave - Looking at my laptop where all works, the path on the launcher Config menu for all apps is C:\DXLab, whereas as you will see in the screen shot of the DT version all (except the Launcher) start as C:\ProgramFiles. So, do I need to delete the "ProgramFiles" part of the paths to make this work?

+ Not unless you'll enjoy wiping your C: drive and re-installing Windows. You cannot delete folders contains installed DXLab applications without corrupting entries in the Windows Registry, and losing the ability to properly "uninstall" those applications.

I sent the Screen shot again to your ambersoft address.

+ I have the screen shot, thanks. It shows that your DXLab applications are/were installed in c:\program files\DXLab Suite  - but the Launcher does not see them as present there now. That's why the "Installed" column on the Configuration window's "DXLab Apps" panel is blank.

+ When you use Windows Explorer to start Commander, in what folder are you finding the

CI-V Explorer.exe

+ file that you are starting?

        73,

               Dave, AA6YQ






TQSL issue

Randy Lake
 

Gm all. I was doing my QSL'ing from the VHF contest this weekend this morning and a note popped up that a new ver of TQSL was available, so I tried to update. During the install I got a missing or corrupted CAB1.CAB file. I went to find the file and delete and start over and the TQSL folder and files are no longer on my machine and it will not let me do a clean install. I get the same error. Attached is the errorlog from this morning.
Any thoughts or suggestions?
Thank you

--
Randy Lake N1KWF
73 Gunn Rd.
Keene,NH


Re: WinWarbler macro suggestion

Dave AA6YQ
 

* More AA6YQ comments below

I think he wants to transmit his POTA (SIG) information during the
QSO, before it's logged.

+ One's own POTA information does not change from QSO to QSO; that information can simply be specified in the macro.
He's trying to avoid having to change it in two places (the myQTH and the macros) each time he activates a new park. It seems like a reasonable request (you already have macros for other items from myQTH).... although I don't operate POTA.

* Thanks, Iain, I understand now.

* since there is no POTA item on the myQTH tab of DXKeeper's Configuration window, the myQTH tab's SIG item is being used to capture "my POTA".

* An alternative would be to

1. add POTA, SOTA, and WWFF items to DXKeeper's "my QTHs" tab

2. define <pota>, <sota>, and <wwff> QSL substitution commands in DXKeeper to permit this information to be included on a QSL card or label

3. extend WinWarbler with <mypota>, <mysota>, and <mywwff> macros to reference these new items


* Or would everyone be satisfied with using the myQTH tab's existing Sig item for POTA, SOTA, and WWFF codes, in which case the original request for <mysig> macro in WinWarbler would be sufficient?

73,

Dave, AA6YQ


Re: I screwed up.

iain macdonnell - N6ML
 

On Sun, Sep 13, 2020 at 9:52 PM iain macdonnell - N6ML via groups.io
<ar=dseven.org@groups.io> wrote:

On Sun, Sep 13, 2020 at 2:08 PM Robert galambos <va3bxg@...> wrote:
When I already Sent a card, i want to rely on lotw, eqsl rather than a physical card for confirmation (like to collect cards) and I want to reduce the cost postage for those call I already sent a qsl card to.

Also Don't want to send another card to someone who at the end will not confirm send a hard them selves

The sql query assumes that I know which call signs have fallen into those category, but I do not
So you're invoking "Add Needed" (or maybe "Add Requested"), but you
want to exclude any stations (calls) to whom you've already sent a
card for another QSO?

You could first filter your log with this expression:

QSL_SENT<>'Y' and Call not in (SELECT DISTINCT Call FROM QSOs WHERE
QSL_Sent='Y')

then invoke "Add Needed" (or "Add Requested"), and decline the offer
to remove the filter that you just applied.

Depending on the size of your log, application of the filter could
take a very long time (during which DXKeeper will appear
unresponsive). I'm not quite sure why it takes so long, actually.
Curiously, removing "not" from the expression (which means it'd match
Callsigns that you *have* sent cards too) is quite fast, but
unfortunately not useful for your problem.
Ahh, I think I found a way to leverage the faster filter. It's
slightly more "involved"....

On the Log QSOs tab, click "Adv".

In the "Advanced Sorts, Filters, & Modifiers Window, in the "Modify
QSOs..." panel at the bottom, select field "APP_DXKeeper_SELECT" and
new value "Y", then click Mod.

Back on the Log QSOs tab of the main window, in the Filter panel at
the bottom, enter this SQL expression:

Call in (SELECT DISTINCT Call FROM QSOs WHERE QSL_Sent='Y')

and then Control-S to apply it. This should match only QSOs with
stations that you've sent a card to.

Look for the "Sel" button in the Filter panel. If you don't see it,
click the "~" button until you do. CONTROL-Click on the "Sel" button.
This will set SELECT to "N" for all QSOs with stations that you have
already sent a card to.

Proceed to the QSL tab and "Add Needed" (etc.) as required.

73,

~iain / N6ML


Re: I screwed up.

iain macdonnell - N6ML
 

On Sun, Sep 13, 2020 at 2:08 PM Robert galambos <va3bxg@...> wrote:
When I already Sent a card, i want to rely on lotw, eqsl rather than a physical card for confirmation (like to collect cards) and I want to reduce the cost postage for those call I already sent a qsl card to.

Also Don't want to send another card to someone who at the end will not confirm send a hard them selves

The sql query assumes that I know which call signs have fallen into those category, but I do not
So you're invoking "Add Needed" (or maybe "Add Requested"), but you
want to exclude any stations (calls) to whom you've already sent a
card for another QSO?

You could first filter your log with this expression:

QSL_SENT<>'Y' and Call not in (SELECT DISTINCT Call FROM QSOs WHERE
QSL_Sent='Y')

then invoke "Add Needed" (or "Add Requested"), and decline the offer
to remove the filter that you just applied.

Depending on the size of your log, application of the filter could
take a very long time (during which DXKeeper will appear
unresponsive). I'm not quite sure why it takes so long, actually.
Curiously, removing "not" from the expression (which means it'd match
Callsigns that you *have* sent cards too) is quite fast, but
unfortunately not useful for your problem.

Maybe there's a better way to solve the problem........

73,

~iain / N6ML


Re: WinWarbler macro suggestion

iain macdonnell - N6ML
 

On Sun, Sep 13, 2020 at 7:22 PM Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

I think he wants to transmit his POTA (SIG) information during the
QSO, before it's logged.

+ One's own POTA information does not change from QSO to QSO; that information can simply be specified in the macro.
He's trying to avoid having to change it in two places (the myQTH and
the macros) each time he activates a new park. It seems like a
reasonable request (you already have macros for other items from
myQTH).... although I don't operate POTA.

73,

~iain


Re: DXKeeper Import?

Dave AA6YQ
 

+ AA6YQ comments below

You know, on sober reflection, it MIGHT be that the program I'm using is European. If so, I'm wondering if they're using the european "comma instead of a period for a decimal point" thing.... In other words, what I thought was "7225" was being stored as "7 comma 225". So DXKeeper, being in "American" units, was seeing this as 7225 MHz, not 7.225 MHz. Make sense?

+ No. ADIF states that the FREQ field's data type is NUMBER, whose definition states that the "decimal point" character is the period character:

<http://adif.org.uk/311/ADIF_311_annotated.htm#Number>

+ The point of an interchange specification is to enable the reliable transfer of information from one application to another without having to worry about locales or "number of bits in a word" or ...

+ Your logging application is not ADIF-compliant.

73,

Dave, AA6YQ


Re: DXKeeper Import?

Richard Perry
 

Thanks, Dave, I'll give it a try. 

You know, on sober reflection, it MIGHT be that the program I'm using is European. If so, I'm wondering if they're using the european "comma instead of a period for a decimal point" thing.... In other words, what I thought was "7225" was being stored as "7 comma 225". So DXKeeper, being in "American" units, was seeing this as 7225 MHz, not 7.225 MHz. Make sense? Anyway, dunno for sure, but I'll let you know if your solution works in the morning.

For future reference, the program I'm using on Android is "VLSLogger". Has a nice feature set, but I do need to solve this issue.

Thanks again and 73 DE AJ0V


On Sun, Sep 13, 2020 at 11:00 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Sorry for the newbie question here guys, but I'm a little stuck.

+ Welcome to DXLab, Richard. There's no need for a pre-apology; all questions are welcome here.


I do a fair amount of POTA and I just switched from a paper log to an Android tablet in the field. It produces ADIF logs.

I tried to import them into my main (DXKeeper) log and had a problem. The TXSent in the Android log is recorded in KHz, not MHz, (for example, 7.225 is seen as 7225.0) so when I import them, DXKeeper throws an error as the frequency doesn't match the band that I say I was on (40 meters).

+ ADIF requires frequencies to be specified in MHz, not KHz. See

<http://adif.org.uk/311/ADIF_311_annotated.htm#QSO_Field_FREQ>


Any work around other than hand hacking this? Please?

+ Yes: please follow these steps:

+ 1. make a backup copy of your log (Configuration window, Log tab, Backup button)

+ 2. on the Main window's "Log QSOs" tab

+ 2a. click the X button in the Filter panel at the bottom of the  tab so that all QSOs in your Log are present in the Log Page Display

+ 2b. click the Adv button above the Log Page Display to display the "Advanced Sorts, Filters, and Modifiers" window

+ 3. In the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window

+ 3a. set the  "Item name" selector to Freq

+ 3b. type the following into the "Item new value" box:

/ 1000

+ 3c. click the Mod button

+ Every QSO in your log should now have its frequency correctly specified in MHz.

          73,

                 Dave, AA6YQ




--
Regards -
 
Richard T Perry


Re: DXKeeper Import?

Dave AA6YQ
 

+ AA6YQ comments below

Sorry for the newbie question here guys, but I'm a little stuck.

+ Welcome to DXLab, Richard. There's no need for a pre-apology; all questions are welcome here.


I do a fair amount of POTA and I just switched from a paper log to an Android tablet in the field. It produces ADIF logs.

I tried to import them into my main (DXKeeper) log and had a problem. The TXSent in the Android log is recorded in KHz, not MHz, (for example, 7.225 is seen as 7225.0) so when I import them, DXKeeper throws an error as the frequency doesn't match the band that I say I was on (40 meters).

+ ADIF requires frequencies to be specified in MHz, not KHz. See

<http://adif.org.uk/311/ADIF_311_annotated.htm#QSO_Field_FREQ>


Any work around other than hand hacking this? Please?

+ Yes: please follow these steps:

+ 1. make a backup copy of your log (Configuration window, Log tab, Backup button)

+ 2. on the Main window's "Log QSOs" tab

+ 2a. click the X button in the Filter panel at the bottom of the tab so that all QSOs in your Log are present in the Log Page Display

+ 2b. click the Adv button above the Log Page Display to display the "Advanced Sorts, Filters, and Modifiers" window

+ 3. In the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window

+ 3a. set the "Item name" selector to Freq

+ 3b. type the following into the "Item new value" box:

/ 1000

+ 3c. click the Mod button

+ Every QSO in your log should now have its frequency correctly specified in MHz.

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave - Looking at my laptop where all works, the path on the launcher Config menu for all apps is C:\DXLab, whereas as you will see in the screen shot of the DT version all (except the Launcher) start as C:\ProgramFiles. So, do I need to delete the "ProgramFiles" part of the paths to make this work?

+ Not unless you'll enjoy wiping your C: drive and re-installing Windows. You cannot delete folders contains installed DXLab applications without corrupting entries in the Windows Registry, and losing the ability to properly "uninstall" those applications.

I sent the Screen shot again to your ambersoft address.

+ I have the screen shot, thanks. It shows that your DXLab applications are/were installed in c:\program files\DXLab Suite - but the Launcher does not see them as present there now. That's why the "Installed" column on the Configuration window's "DXLab Apps" panel is blank.

+ When you use Windows Explorer to start Commander, in what folder are you finding the

CI-V Explorer.exe

+ file that you are starting?

73,

Dave, AA6YQ


DXKeeper Import?

Richard Perry
 

Sorry for the newbie question here guys, but I'm a little stuck. I do a fair amount of POTA and I just switched from a paper log to an Android tablet in the field. It produces ADIF logs.

I tried to import them into my main (DXKeeper) log and had a problem. The TXSent in the Android log is recorded in KHz, not MHz, (for example, 7.225 is seen as 7225.0) so when I import them, DXKeeper throws an error as the frequency doesn't match the band that I say I was on (40 meters).

Any work around other than hand hacking this? Please?

Thanks - 

Richard Perry AJ0V