KB6IBB SWL Logger Activity
A shortwave listening logger for shortwave and amateur radio.
Brought to you by:
kb6ibb
Activity for KB6IBB SWL Logger
-
KB6IBB SWL Logger released /SWL Logger-V5/KB6IBB-SWLLogger500-3LTS-Win64.zip
-
-
-
-
-
-
-
-
-
Jeff Stillinger modified ticket #10
Log import from version 4
-
2024-03-05 - Version 4.6.1-4 update released that fixes the reported bug. Instructions for a resolution was given to the reporting party, no further problems reported. At this time, issue is resolved and the ticket is closed. //KB6IBB
-
-
-
-
James Darrow posted a comment on ticket #10
That did it. All records imported and working on version 5. Thanks again!! 73 Jim, KB9MMC On 02/03/2024 17:26, Jeff Stillinger wrote: Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This is going to be time consuming, but, no other way to do it. You just have to look at the Date End and correct the dates that are not in long...
-
Thanks Jeff, I'll go back and take a look. It sounds like that may have been the time when I was transferring things from my old logging software, transferring 500 files by hand wasn't fun. Thanks again for the help. 73 Jim, KB9MMC On 02/03/2024 17:26, Jeff Stillinger wrote: Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This...
-
2024-03-02 - Received the end users database file and reviewed it for errors. Several date format errors were noted. Provided corrective action instructions to the end user. Issued a HIGH PRIORITY bug fix for version 4.6 to ensure mis-formatted dates will not be saved to the database. Update pending. Support ticket will remain in Pending status until the 4.6 update is issued. //KB6IBB
-
Found it!! Exactly what I though it was. A rouge date that somehow made it in. Note the March 12th Date End, missing a "/" character which caused the date to not be saved in the long date format. I found about 10 of them. This is going to be time consuming, but, no other way to do it. You just have to look at the Date End and correct the dates that are not in long date format record by record using Version 4.6. At least you have less than a 1,000 records to review. Once they are all saved accordingly,...
-
Hey Jeff, Here are both ways name changed to a PDF and a compressed version. Yes I'm using the February 28th release. After a few attempts I went to the beta version but when I got the same error message I went back to the latest release. It also appeared at a quick glance it looked like there wasn't as many catagories in version 5 for the type of station. I'll look again. Thanks!! Jim, KB9MMC On 02/03/2024 15:02, Jeff Stillinger wrote: Hi James, I don't see the attachment. Possibly being filtered...
-
Hi James, I don't see the attachment. Possibly being filtered by one of our ISPs. See if you can try sending it as a zip file or rename it to a .pdf to fool the A.I. I really do need to see the file. I suspect there may be a rouge date entry in the data somewhere. I appreciate your patients during our growing pains as we move the logger from a smaller U.S. user base to a much larger world wide user base. Date/Time in a international format was the biggest feature request from our new and developing...
-
Hi Jeff, Attached is a copy of my version 4 database as requested. Thanks for the help. You have a great piece of software! 73 Jim, KB9MMC On 02/03/2024 03:26, Jeff Stillinger wrote: Hi James, Would it be possible for you to email me your version 4 database? Looking over the code, and our test runs, databases going all the way back to version 2 import without error. I would really need to take a look at yours specifically to track it down. When all is said and done, I will send you back either a...
-
Log import from version 4
-
2024-03-01 - Contact made with end user by private email. Awaiting response from user to email me his Version 4 database for inspection. Conducted a retest in the lab with version 2, 3, and 4 databases with no errors generated. It will be vital to see the version 4 problematic database to troubleshoot the issue. //KB6IBB
-
Hi James, Would it be possible for you to email me your version 4 database? Looking over the code, and our test runs, databases going all the way back to version 2 import without error. I would really need to take a look at yours specifically to track it down. When all is said and done, I will send you back either a database you can import, or just a nice pretty version 5. Whichever you would like. On 3/1/24 19:23, James Darrow wrote: [tickets:#10] Log import from version 4 Status: open Milestone:...
-
Log import from version 4
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >