locked Re: [Ham-Apps] Lost Logbook

Laurie, VK3AMA <groups03@...>


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:

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!


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: 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

Join Support@HamApps.groups.io to automatically receive all group messages.