Well the fact that I had 2024 in the QSO_End doesn't help. Sorry about that.
toggle quoted message
Show quoted text
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Bob Main via groups.io Sent: Wednesday, April 2, 2025 2:43 PM To: DXLab@groups.io Subject: Re: [DXLab] Change QSL Sent to "N" I tried the statement you have below and it didn't like it, so I changed it to: QSO_Begin #2025-04-02 1300# AND QSO_End #2024-04-02 1400# It didn't like that either. I'll do some digging later and see if I can figure out what's wrong. I'm sure it is something simple. 73, Bob KB4CL -----Original Message----- From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV Sent: Wednesday, April 2, 2025 11:46 AM To: DXLab@groups.io Subject: Re: [DXLab] Change QSL Sent to "N" On 2025-04-02 10:49 AM, Bob Main via groups.io wrote: Thanks Joe, no not using contest mode. It is the CWT contests thatQSO_Begin between #2025-04-02 13:00# and #2025-04-02 14:00# should do the job for the first hour this morning. That becomes QSO_Begin between #2025-04-02 19:00# and #2025-04-02 20:00# for this afternoon's run, etc. Given the amount of changing (four times a week) and short duration, it would probably be just as easy to use the UTC filter in DXK Advanced Sorts, Filters & Modifiers. Select the After radio button, enter the same data as in the two examples above, and click "Filter" at the right end of the panel. You will be in the Advanced Sorts, Filters and Modifiers window to change QSL_Sent to 'N' anyway. 73, ... Joe, W4TV On 2025-04-02 10:49 AM, Bob Main via groups.io wrote: Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame. |