Date   

locked Re: [Ham-Apps] jt-alert

Laurie, VK3AMA <groups03@...>
 

Hi John,

Moving the Halt TX to the titlebar would save one mouse-click.

I will consider your request and if it doesn't make the titlebar visually crowded it may be in the next release.

de Laurie, VK3AMA

On 22-October-2011 17:13, jgmags2000 wrote:
Fabulous! fabulous job Laurie.. All working well. Incredible piece of software, thank you for this gift. One question. Could HAlt/tx be moved to the title bar using only 1 click instead of going into set up?

Again, thanks Laurie

73, John KJ1J


locked jt-alert

jgmags2000 <jgmags2000@...>
 

Fabulous! fabulous job Laurie.. All working well. Incredible piece of software, thank you for this gift. One question. Could HAlt/tx be moved to the title bar using only 1 click instead of going into set up?

Again, thanks Laurie

73, John KJ1J


locked Re: [Ham-Apps] JT-Alert 1.5.1 now available for download.

Laurie, VK3AMA <groups03@...>
 

HI David,

It is using the same linux/Wine code as the test version you have been running. Your version doesn't include all the additional bugfixes or changes. I recommend you install this new version.

73 de Laurie, VK3AMA

On 22-October-2011 11:21, David wrote:
Hi Laurie..is this version compatible with Wine
under Linux

73 David VK4BDJ




On 22/10/11 08:59, Laurie, VK3AMA wrote:
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:

  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA



locked Re: [Ham-Apps] JT-Alert 1.5.1 now available for download.

BuDJie
 

Hi Laurie..is this version compatible with Wine
under Linux

73 David VK4BDJ




On 22/10/11 08:59, Laurie, VK3AMA wrote:
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:

  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA



locked JT-Alert 1.5.1 now available for download.

Laurie, VK3AMA <groups03@...>
 


JT-Alert 1.5.1 is now available for download at http://Ham-Apps.com/

This version contains important Bug Fixes. It is recommended this version is installed.
 
Note: There is no help file at present.

Note: JT-Alert 1.5.1 comes bundled with Sounds and Callsign databases (US States, LoTW & eQSL) for WAS alerts and Callsign flagging of LoTW/eQSL membership. In a future release, these databases will be moved to a separate installer with an integrated updater. Sounds will also be moved, in a future release, to a separate installer.

Install Instructions:
  1. Uninstall 1.5.0.
  2. Download either the Male or Female voice JT-Alert setup file.
  3. Run the newly downloaded file and install to a directory of your choice (it is OK to install the Program Files directory tree of Vista or Win7 as files that are modified and/or created by JT-Alert are store in the Users Local AppData area so there are no security issues).
  4. While JT-Alert is running, click the word "Settings" in the title-bar and click "Configuration..." on the displayed menu.
  5. In the Configuration window check that your settings are still correct.
  6. Close the Configuration window, saving the settings.
  7. JT-Alert 1.5.1 is now setup.
From the Release notes:
  New    - HRDV5 & DXKeeper options to flag QSO with LoTW/eQSL upload requested.
  New    - Additional error detection and warning of inability to locate
            the JT65-HF log file and or path.
  New    - Support for multi-monitor PCs when moving and restoring windows.
  New    - Option to not use Memory Cache for DB query results.
            (Only enable if advised by Support)
  New    - Warning if log & database files specified in Config don't exist.
            (file paths will get reset to blank in Config after this warning)
  Change - Removed pop-up window display timeout for failed QSO logging.
  Change - Logging Configuration layout for clearer understanding of which log
            is active. Enabling one log force disables other logs.
  Change - JT65-HF Notes now logged to HRDV5 Comments field.
  BugFix - Callsign not shown as B4 after failed QSO Log message.
  BugFix - Failed Log message when QSO was correctly logged due to timing.
  BugFix - Windows Regional Settings with non-dot used as decimal separator
            caused logging failures and SQL error messages.
  BugFix - Config window position off screen.
  BugFix - HRDV5 log crash when missing DXCC code logged.
  BugFix - HRDV5 QSOs being flagged as SWL rather than normal contact.
  BugFix - DXLab Workspaces caused JT-Alert Configuration to abort.
  BugFix - Spaces in JT65-HF Log path or no trailing backslash caused no logging.
  BugFix - Sound OFF setting not being remembered between restarts.
  BugFix - Out of Shack alert not correctly toggling Wanted Calls check mark.
  BugFix - JT-Alert always on top not working.
  BugFix - DXKeeper Lookup on new JT65-HF "TX to Call Sign" entry not working.

If you experience problems or have questions post a message to the Ham-Apps Yahoo Group.
Please DON'T reply to this message with your questions.
Start a new message with a subject line that reflects the question or problem.

Enjoy,
de Laurie, VK3AMA


locked Re: [Ham-Apps] Logging problems

John <john@...>
 

Hi Laurie.
We have visitors tonight so I will go through all your suggestions in the morning!

One quick thing is that the B4 path is actually there and is pointing to the same database used in 1.4.1 it was the path to the ADIF log file which had disappeared. I put it back in but still had the problems described.
I follow what you say about JT-Alert not locking the file but the strange thing is that it has worked, and still does work perfectly with version 1.4.1 which makes me think that JT65-HF and ADIF Master are not the culprits.

I'm running AVG Free, the latest 2012 version.

As I said I will work through your suggestions very carefully in the morning when the visitors leave. As always I appreciate all your help and it really is not a major problem because I can still use V1.4.1.

Very many thanks.
73,
John.

On 21/10/2011 21:54, Laurie, VK3AMA wrote:
 

Hi John,

I will answer you questions in reverse order.

The "Sound OFF" setting being remembered between JT-Alert restarts is implemented in 1.5.1 (due for release today)

The missing B4 log path is by design. When JT-Alert first starts and reads your configuration file, any file specified in the configuration is tested to see if the file exists. If the file no longer exists, the setting is cleared and the configuration will show an empty field. If your field is being cleared, but on further investigation you find that the file does exists, then that suggests that something on your PC is preventing JT-Alert from reading your file system accurately (Virus software maybe) and that will require further investigation.

Your ADIF issue. I assume you are opening the JT65-HF adi log file and editing that in ADIF master. Is that correct?
JT-Alert 1.4.1 never looked at the JT65-HF log file, but 1.5.0 does, but it attempts to open the file once and in read-only mode only (after a Log QSO command) to determine the QSO data. This fileopen action, if it fails (due to permissions or locking) is never repeated and just returns no data to JT-Alert. JT-Alert doesn't open the file in write mode or apply any locks to the file and doesn't alter the adi file in any way. So if ADIF Master is reporting that the file is not of the correct format, then that suggests that a program other than JT-Alert has modified the file, that leaves either ADIF master or JT65-HF.

Having said all that, there seems to be some sort of PC file-system issue at play here. What virus software are you running? Have you tried disabling that. There have been no other reports of this issue, yours is the first, again leading me to think that it is specific to your PC environment.

As an alternative, have you tried logging to a JT-Alert created ADIF file (visit the logging section of JT-Alert configuration) and opening that file in ADIF Master and avoid opening the JT65-HF adi log.

Regards
Laurie, VK3AMA


On 22-October-2011 02:58, g4gcl wrote:

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked Re: [Ham-Apps] Logging problems

Laurie, VK3AMA <groups03@...>
 

Hi John,

I will answer you questions in reverse order.

The "Sound OFF" setting being remembered between JT-Alert restarts is implemented in 1.5.1 (due for release today)

The missing B4 log path is by design. When JT-Alert first starts and reads your configuration file, any file specified in the configuration is tested to see if the file exists. If the file no longer exists, the setting is cleared and the configuration will show an empty field. If your field is being cleared, but on further investigation you find that the file does exists, then that suggests that something on your PC is preventing JT-Alert from reading your file system accurately (Virus software maybe) and that will require further investigation.

Your ADIF issue. I assume you are opening the JT65-HF adi log file and editing that in ADIF master. Is that correct?
JT-Alert 1.4.1 never looked at the JT65-HF log file, but 1.5.0 does, but it attempts to open the file once and in read-only mode only (after a Log QSO command) to determine the QSO data. This fileopen action, if it fails (due to permissions or locking) is never repeated and just returns no data to JT-Alert. JT-Alert doesn't open the file in write mode or apply any locks to the file and doesn't alter the adi file in any way. So if ADIF Master is reporting that the file is not of the correct format, then that suggests that a program other than JT-Alert has modified the file, that leaves either ADIF master or JT65-HF.

Having said all that, there seems to be some sort of PC file-system issue at play here. What virus software are you running? Have you tried disabling that. There have been no other reports of this issue, yours is the first, again leading me to think that it is specific to your PC environment.

As an alternative, have you tried logging to a JT-Alert created ADIF file (visit the logging section of JT-Alert configuration) and opening that file in ADIF Master and avoid opening the JT65-HF adi log.

Regards
Laurie, VK3AMA


On 22-October-2011 02:58, g4gcl wrote:

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked Logging problems

g4gcl <john@...>
 

Hi Laurie.

I'm having strange problems with logging using 1.5.0.

I have a very simple setup which works fine with 1.4.1. I just have an ADIF file  and my normal sequence before 1.5.0 was:-

QSO

Log QSO - Fill in details

Open ADIF with ADIF Master and update extra things for EQSL such as comments.

I could leave ADIF Master open and the only thing I had to do was to make it re-read the file so that I could see the latest entries.

Now with 1.5.0 I get an error when I log the QSO and it asks me if I want to quit or carry on & risk data corruption. I usually quit and then spend quite a long time trying to find out what's wrong and load the QSO into the log file.

After this error if I try to open the file with ADIF Master it says the file is not the correct format. If I close 1.5.0 then ADIF Master will open it.

The only reliable way to log is either to have 1.5.0 closed down or use 1.4.1 which has non of these problems.

 

I really hope that's clear & you have some ideas! One last thing the B4 part seems to have stopped working today and I found that the log file path had disappeared, I've fixed that but I'm not sure if it's working now because of all the time sorting this other problem out. By the way I accidentally said yes to saving the QSO & possibly causing corruption & it added the previous QSO again but with the "m" missing from 10m! Very odd

One last thing Laurie. In future releases would it be possible to turn the sound off and save that option? Several times I have not noticed that it has been on because it resets every time it runs and it occasionally causes the program to crash.

That will teach you to comment about things being quiet!

73,

John.


locked Re: [Ham-Apps] Re: Test email. Please ignore

John <john@...>
 

Make the most of the silence Laurie :-D

73, John

On 21/10/2011 09:18, Laurie wrote:
 

Received OK.
Must be just a very quiet day on Yahoo today.

--- In Ham-Apps@..., "Laurie, VK3AMA" wrote:
>
> Testing if Yahoo Groups is having message posting/delivery problems today.
> posted @ 0816 21-Oct utc
>
> de Laurie, VK3AMA
>


locked Re: Test email. Please ignore

Laurie <groups03@...>
 

Received OK.
Must be just a very quiet day on Yahoo today.

--- In Ham-Apps@yahoogroups.com.au, "Laurie, VK3AMA" <groups03@...> wrote:

Testing if Yahoo Groups is having message posting/delivery problems today.
posted @ 0816 21-Oct utc

de Laurie, VK3AMA


locked Test email. Please ignore

Laurie, VK3AMA <groups03@...>
 

Testing if Yahoo Groups is having message posting/delivery problems today.
posted @ 0816 21-Oct utc

de Laurie, VK3AMA


locked Re: [Ham-Apps] mixw

David Pykett
 

Thanks Laurie, I look forward to 1.5.2 release whenever you get time to do it.
 
73
 
Dave
G0IIQ


 
 

Hi Dave,

Its on my "To be Implemented List".
It wont be in the upcoming 1.5.1 release due in about 2 days.

It will most likely be in the 1.5.2 release, but timing on that is unknown at this time.

de Laurie, VK3AMA


On 20-October-2011 07:16, David Pykett wrote:

,___


locked Re: [Ham-Apps] Lost Logbook

Scott
 

Laurie,

I just got it and downloading it from Dropbox right now. Wow, it sure is a lot smaller file now. I'll let you know how it goes. Maybe a bunch more emails will be coming tonight? Thank you very much for the personal attention you gave me tonight.

73 Scott
KN3A


On Wed, Oct 19, 2011 at 10:02 PM, Scott L. <scolit@...> wrote:
Laurie,

I'm really sorry, I'm getting nothing on Gmail from you at all. I have no spam filters set or anything. They're just not getting to me. Try sending to scottpa1960@... is the only other thing I can say to try.

Scott


On Wed, Oct 19, 2011 at 10:00 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Scott,

I was replying to your original direct email, the address was correct. Have resent again using one of my other (one of many) email addresses, this time also a Gmail account.

Laurie, VK3AMA



On 20-October-2011 12:49, Scott L. wrote:
Laurie,

I check my spam folder - no emails at all. You're doing scolit@... when you send? If you use GTalk, I can be reached on there too as scolit@... if you want to send me the link that way. I'm really astounded that I'm not getting your emails??

Scott

On Wed, Oct 19, 2011 at 9:46 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Scott,

Resent. The email contains links to beta files and Gmail may have see the email as spam. Check your spam folder

Laurie, VK3AMA




On 20-October-2011 12:38, Scott L. wrote:
Laurie,

No, I did not. Sorry. Can  you send it again to me? My direct email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott

On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
 

Scott   

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

 

The files maybe hidden,   if you cant see them, in which case you need to “show” them

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

 

 

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

 








locked Re: [Ham-Apps] Lost Logbook

Scott
 

Laurie,

I'm really sorry, I'm getting nothing on Gmail from you at all. I have no spam filters set or anything. They're just not getting to me. Try sending to scottpa1960@... is the only other thing I can say to try.

Scott


On Wed, Oct 19, 2011 at 10:00 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Scott,

I was replying to your original direct email, the address was correct. Have resent again using one of my other (one of many) email addresses, this time also a Gmail account.

Laurie, VK3AMA



On 20-October-2011 12:49, Scott L. wrote:
Laurie,

I check my spam folder - no emails at all. You're doing scolit@... when you send? If you use GTalk, I can be reached on there too as scolit@... if you want to send me the link that way. I'm really astounded that I'm not getting your emails??

Scott

On Wed, Oct 19, 2011 at 9:46 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Scott,

Resent. The email contains links to beta files and Gmail may have see the email as spam. Check your spam folder

Laurie, VK3AMA




On 20-October-2011 12:38, Scott L. wrote:
Laurie,

No, I did not. Sorry. Can  you send it again to me? My direct email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott

On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
 

Scott   

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

 

The files maybe hidden,   if you cant see them, in which case you need to “show” them

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

 

 

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

 







locked Re: [Ham-Apps] Lost Logbook

Laurie, VK3AMA <groups03@...>
 

Scott,

I was replying to your original direct email, the address was correct.
Have resent again using one of my other (one of many) email addresses,
this time also a Gmail account.

Laurie, VK3AMA

On 20-October-2011 12:49, Scott L. wrote:


Laurie,

I check my spam folder - no emails at all. You're doing
scolit@gmail.com <mailto:scolit@gmail.com> when you send? If you use
GTalk, I can be reached on there too as scolit@gmail.com
<mailto:scolit@gmail.com> if you want to send me the link that way.
I'm really astounded that I'm not getting your emails??

Scott

On Wed, Oct 19, 2011 at 9:46 PM, Laurie, VK3AMA <groups03@vkdxer.com
<mailto:groups03@vkdxer.com>> wrote:

Scott,

Resent. The email contains links to beta files and Gmail may have
see the email as spam. Check your spam folder

Laurie, VK3AMA




On 20-October-2011 12:38, Scott L. wrote:
Laurie,

No, I did not. Sorry. Can you send it again to me? My direct
email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott

On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA
<groups03@vkdxer.com <mailto:groups03@vkdxer.com>> wrote:

Hi Scott,

Did you get my email with the DropBox link to your repaired
log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the
.mdb one? He's got the My Logbook.mdb from my dropbox link I
sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@gmail.com
<mailto:scolit@gmail.com>> wrote:

Don,

I believe I can see all hidden folders. I know when I
had to start over a week ago with the new hard drive,
there was a setting to view hidden folders because I
originally wasn't able to view "appdata" which was
hidden. Is it possible there's hidden files within just
the HRD Logbook? I see HRD My Logbook.ldb and HRD My
Logbook.mdb. I sent Laurie a link to Dropbox which
includes my HRD My Logbook.mbd - hope that helps him.
Or, if there's another way to bring hidden folders in
this specific directory, I'd like to know how to enable
them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch
<don@orcon.net.nz <mailto:don@orcon.net.nz>> wrote:

Scott

Try .................
c:/users/yourname/appdata/roaming/simon brown
hb9drv/hrd logbook/HRD mylogbook.dat

The files maybe hidden, if you cant see them, in
which case you need to “show” them

Don zl1atb

*From:*Ham-Apps@yahoogroups.com.au
<mailto:Ham-Apps@yahoogroups.com.au>
[mailto:Ham-Apps@yahoogroups.com.au
<mailto:Ham-Apps@yahoogroups.com.au>] *On Behalf Of
*Scott L.
*Sent:* Thursday, 20 October 2011 12:03 p.m.
*To:* Ham-Apps@yahoogroups.com.au
<mailto:Ham-Apps@yahoogroups.com.au>


*Subject:* Re: [Ham-Apps] Lost Logbook

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I
am using HRDV5, using Win7. What is the name of this
file? And, once I get my logbook back, I would be
very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA
<groups03@vkdxer.com <mailto:groups03@vkdxer.com>>
wrote:

Scott,

you can send the log file (I assume you are using a
MS Access file under HRDV5) direct to the email
address that should be visible in this email.

The extra log fields was provided so that items like
Name, QTH, and other data that user may wish to have
in the log and is not provided by JT65-HF, will get
saved to the log when logging is complete. This was
provided to avoid the need to then access the HRD,
DXKeeper, whatever logging application to add/change
that information after it was in the log.

Clicking in those fields shouldn't have produced the
problem you saw. I have added some additional error
checking into the logging code to do an additional
callsign DXCC check (if it is missing) to avoid
logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In
this new version, I have been unable to break the
HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At
this point I don't think I'm going to be able to
do this, plus I'm going to have to ask you what
exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know
this morning while working a Russian station I
wanted to see what the Log Field does, and it
appeared it had no use to me. I'm wondering if
just the fact I had that enabled and I had
clicked in a couple of those fields that I had
this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA
<groups03@vkdxer.com
<mailto:groups03@vkdxer.com>> wrote:

Hi Scott,

If you are uncomfortable with manually
editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code
field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce
that happening is to log a
callsign using the JT65-HF "Log Contact"
window and entering the
Callsign there while there is no callsign
entered on the main JT65-HF
window in the "TX to Call Sign" field.
JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU,
etc. Since that data is
missing, because of the no callsign, no DXCC
is Sent to the HRD log.

I am working on the fix. I had never
anticipated people would log
without first having the QSO entered on the
main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT
Alert since I downloaded it on Sunday, and
have probably logged over 100 QSO's
successfully. This morning I worked two JT65
QSO's on 10 meters and logged them. When I
did a refresh on the logbook, I got an error
(see logfile). I tried to do a repair of the
database and got a message Driver's
ConfigDSN, ConfigDriver, or COnfigTranslator
failed.
>
> Can you help me out here? I have Win7 64
bit, the latest V5.2893, and 1.0.7. Any
ideas please? Until this morning it's been
completely trouble free and I love the JT
Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My
Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook
- Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT
COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO
L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO
L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED
FROM [TABLE_HRD_CONTACTS_V01] ORDER BY
COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character
value for cast specification on column
number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in
1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>





locked Re: [Ham-Apps] Lost Logbook

Scott
 

Laurie,

I check my spam folder - no emails at all. You're doing scolit@... when you send? If you use GTalk, I can be reached on there too as scolit@... if you want to send me the link that way. I'm really astounded that I'm not getting your emails??

Scott


On Wed, Oct 19, 2011 at 9:46 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Scott,

Resent. The email contains links to beta files and Gmail may have see the email as spam. Check your spam folder

Laurie, VK3AMA




On 20-October-2011 12:38, Scott L. wrote:
Laurie,

No, I did not. Sorry. Can  you send it again to me? My direct email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott

On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
 

Scott   

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

 

The files maybe hidden,   if you cant see them, in which case you need to “show” them

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

 

 

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

 






locked Re: [Ham-Apps] Lost Logbook

Laurie, VK3AMA <groups03@...>
 

Scott,

Resent. The email contains links to beta files and Gmail may have see the email as spam. Check your spam folder

Laurie, VK3AMA


On 20-October-2011 12:38, Scott L. wrote:
Laurie,

No, I did not. Sorry. Can� you send it again to me? My direct email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott

On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA <groups03@...> wrote:
�

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
�

Scott���

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

�

The files maybe hidden,�� if you cant see them, in which case you need to �show� them

Don zl1atb

�

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

�

�

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

�

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

�

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

�





locked Re: [Ham-Apps] Lost Logbook

Scott
 

Laurie,

No, I did not. Sorry. Can  you send it again to me? My direct email is scolit(at) gmail(dot)com

Thanks for fixing!

Scott


On Wed, Oct 19, 2011 at 9:37 PM, Laurie, VK3AMA <groups03@...> wrote:
 

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA



On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
 

Scott   

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

 

The files maybe hidden,   if you cant see them, in which case you need to “show” them

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

 

 

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

 





locked Re: [Ham-Apps] Lost Logbook

Don Leitch <don@...>
 

I am really not sure  which one he needs , I am only getting to grips with windows 7, I have been an xp user ,for so long and this new system gets me . I have only just worked out how to show the attributes, oops

If he has both then I guess you are safe. Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 2:31 p.m.
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Lost Logbook

 

 

Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:

Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A

 

On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:

 

Scott   

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

 

The files maybe hidden,   if you cant see them, in which case you need to “show” them

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

 

 

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,COL_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

 

 

 


locked Re: [Ham-Apps] Lost Logbook

Laurie, VK3AMA <groups03@...>
 

Hi Scott,

Did you get my email with the DropBox link to your repaired log file?

No the .ldb file is not needed.

Laurie, VK3AMA

On 20-October-2011 12:30, Scott L. wrote:
Don,

Will Laurie need the HRD My Logbook.ldb in addition to the .mdb one? He's got the My Logbook.mdb from my dropbox link I sent earlier to him.

Scott
KN3A

On Wed, Oct 19, 2011 at 9:14 PM, Scott L. <scolit@...> wrote:
Don,

I believe I can see all hidden folders. I know when I had to start over a week ago with the new hard drive, there was a setting to view hidden folders because I originally wasn't able to view "appdata" which was hidden. Is it possible there's hidden files within just the HRD Logbook? I see HRD My Logbook.ldb and HRD My Logbook.mdb. I sent Laurie a link to Dropbox which includes my HRD My Logbook.mbd - hope that helps him. Or, if there's another way to bring hidden folders in this specific directory, I'd like to know how to enable them.

Thanks for your help Don.

Scott
KN3A


On Wed, Oct 19, 2011 at 9:06 PM, Don Leitch <don@...> wrote:
�

Scott���

Try ................. c:/users/yourname/appdata/roaming/simon brown hb9drv/hrd logbook/HRD mylogbook.dat

�

The files maybe hidden,�� if you cant see them, in which case you need to �show� them

Don zl1atb

�

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Scott L.
Sent: Thursday, 20 October 2011 12:03 p.m.
To: Ham-Apps@...


Subject: Re: [Ham-Apps] Lost Logbook

�

�

Laurie,



I see your email address as groups03(at)vkdxer(dot)com.

I'm still not sure what you want me to send you. I am using HRDV5, using Win7. What is the name of this file? And, once I get my logbook back, I would be very happy to beta test for you.

Scott

On Wed, Oct 19, 2011 at 6:59 PM, Laurie, VK3AMA <groups03@...> wrote:

�

Scott,

you can send the log file (I assume you are using a MS Access file under HRDV5) direct to the email address that should be visible in this email.

The extra log fields was provided so that items like Name, QTH, and other data that user may wish to have in the log and is not provided by JT65-HF, will get saved to the log when logging is complete. This was provided to avoid the need to then access the HRD, DXKeeper, whatever logging application to add/change that information after it was in the log.

Clicking in those fields shouldn't have produced the problem you saw. I have added some additional error checking into the logging code to do an additional callsign DXCC check (if it is missing) to avoid logging missing DXCC number to the log.

If you wish to try the new 1.5.1 beta email me. In this new version, I have been unable to break the HRD log.

de Laurie, VK3AMA




On 20-October-2011 09:45, Scott L. wrote:

Laurie,

How and where can I send the log file to? At this point I don't think I'm going to be able to do this, plus I'm going to have to ask you what exact file I'm looking for to send to you.

I don't use the Log Fields feature. I do know this morning while working a Russian station I wanted to see what the Log Field does, and it appeared it had no use to me. I'm wondering if just the fact I had that enabled and I had clicked in a couple of those fields that I had this issue today?

Thanks for your help!

Scott
KN3A

On Wed, Oct 19, 2011 at 3:25 PM, Laurie, VK3AMA <groups03@...> wrote:

�

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA



On 19-October-2011 23:39, Scott wrote:
> Laurie,
>
> I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.
>
> Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!
>
> 73 Scott
> KN3A
>
>
> 08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Opening 'HRD My Logbook - Access'
> 08:29:46 Database Open status 1
> 08:29:46 Database Timeout ..: 120 seconds
> 08:29:46 Database Open status 1
>
> 08:29:47 Reload Error: Getting 24011 records -

> 08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,CO L_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,CO L_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC


> 08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second
>
> 08:29:47 General Loading class CLogfileFrame
>
>

�