Date   

locked Lost Logbook

Scott
 

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,COL_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] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Jeff - K2AK
 

Thank you Laurie,

Very much appreciated.

73 de Jeff K2AK

-----Original Message-----
From: Ham-Apps@yahoogroups.com.au [mailto:Ham-Apps@yahoogroups.com.au] On
Behalf Of Laurie, VK3AMA
Sent: Wednesday, October 19, 2011 5:11 AM
To: Ham-Apps@yahoogroups.com.au
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert
after each contact

Hi Jeff,

That is a defect in JT-Alert 1.5.0 that is corrected in the upcoming
1.5.1 release (2 days time).

de Laurie, VK3AMA

On 19-October-2011 22:10, sitedev wrote:
Everything seems to be working fine with the nicely updated JT-Alert 1.5
except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE
window to capture all of the user information from QRZ or Buckmaster
(Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the
call sign and band to the B4log.mdb file just fine. The next time the call
sign that was previously logged is decoded is doesn't display as worked B4.
If I restart JT65-HF and JT-Alert it will then display that same call sign
as worked B4.

I do have the Display worked B4 checked in the configuration and created
the B4log.mdb file in the default directory and then imported all of my JT65
contacts from HRD. I tried using the log to ADI file but that didn't work at
all unless the callsign was in the ADI file (didn't care what was in B4 mdb
file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff - K2AK
DM41

------------------------------------

Yahoo!7 Groups Links


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Jeff - K2AK
 

Dave,

 

I guess there is no real solution to automating (being lazy) even more. I stopped using HRD Utilities when HRD included LoTW updating. I think the easiest way for me was to try and get the B4Log.mdb working without restarting but I am sure these little tweaks will happen (don’t want to pester the developer as there are more important issues at hand). JT65 is much better with JT-Alert than without, hands down.

 

Laurie… Thanks for your awesome contributions to the Amateur Radio community.

 

73, Jeff

K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Dave Wright
Sent: Wednesday, October 19, 2011 5:00 AM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Jeff,

 

You can either open the window and click the button as you said, or I use HRD Utilities.  It can do group updates…1, 2, 5, 10, all QSOs at once.  And you can select the fields you want to update…for example, I don't have it update the Grid as I want to use what is listed in JT65, but I do like to get names and other info.  

 

It is still a lot easier than typing them in one by one.  


-- 
Dave Wright

K3DCW

 

"Real radio bounces off the sky"

 

On Wednesday, October 19, 2011 at 7:56 AM, K2AK - Jeff wrote:

 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41

 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Laurie, VK3AMA <groups03@...>
 

Hi Jeff,

That is a defect in JT-Alert 1.5.0 that is corrected in the upcoming 1.5.1 release (2 days time).

de Laurie, VK3AMA

On 19-October-2011 22:10, sitedev wrote:
Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff � K2AK
DM41


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Dave Wright <hfradiopro@...>
 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Jeff - K2AK
 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Re: [Ham-Apps] Thanks, Laurie

W5ADD@arrl.net
 

Laurie, hi.

The latest e-mail regarding removal of the blank space in the JT65 log pathname totally did the trick for me.

Congratulations on an update that is scary because it is so good!

--
Parker, W5ADD


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

K. D. Sarchet <wy5r@...>
 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Problems Reading B4log.mdb unless restart JT-Alert after each contact

Jeff - K2AK
 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Re: [Ham-Apps] HRD 5.0->eqsl logging request

Laurie, VK3AMA <groups03@...>
 

HRDV5 QSOs being marked as SWL is corrected and will be the 1.5.1 release.

de Laurie, VK3AMA

On 19-October-2011 11:35, kb0asq wrote:
It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way. I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ


locked Re: [Ham-Apps] HRD 5.0->eqsl logging request

Laurie, VK3AMA <groups03@...>
 

Hi KB0ASQ,

Flagging QSOs with eQSL and or LoTW "Requested" is already coded into the next release which should be out in 2 or 3 days.

Please provide more detail about how a HRD QSO is marked as SWL. (I don't regularly use HRD)



de Laurie, VK3AMA

On 19-October-2011 11:35, kb0asq wrote:
It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way.  I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ




locked HRD 5.0->eqsl logging request

wd0dxd
 

It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way. I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ


locked Re: [Ham-Apps] ## IMPORTANT ## - New Fix for NOT LOGGING errors.

Laurie, VK3AMA <groups03@...>
 

Additional information.

After performing the fix, log 2 QSOs to confirm that fix has worked, the first logging may not work, but the second should be logged.

Sorry for all this run-around.

New release, 1.5.1 in 2 or 3 days.

Laurie, VK3AMA

On 19-October-2011 08:29, Laurie, VK3AMA wrote:
You will need to have the jt65hf_log.adi file located in a directory path that does not contain a space.

The Fix.
  1. Stop JT-Alert.
  2. Start JT65-HF if not running.
  3. Click "Log QSO" button in JT65-HF.
  4. Use the browse button (right side of edit field) to browse to a NEW location (without a space in the path)
  5. Ensure that this new path has a Backslash "\" at the end of the path, type that character in manually.
  6. Click the "Cancel" button.
  7. Stop JT65-HF (this is important for the new change to be saved to the JT65-HF config file)
  8. Start JT65-HF
  9. Start JT-Alert
Logging should now work and a popup should appear after logging.

This fix will not be necessary once JT-Alert 1.5.1 is released (in 2 or 3 days time).


locked JT-Alert 1.5.0 under Wine

BuDJie
 

Hi Laurie
I know your having a hard time with all the problems but
I thought i would give you a good report and i hope it makes you smile and feel better

Im really amazed at what the program can do when just used on its own with
JT65-HF.....I love the Alert tones when you get a answer to your call
I have 2 comps running all the time....this one has e-mail and net working
the other one about 3 meters away has all the Ham apps
go from one to the other on the office chair...if im busy at this comp i now dont miss any contacts on the Ham comp

Most of the crashes happened when using Ubuntu 11.10 with the Unity desktop
(dont like it) have been able to get it to work with Gnome 3 and it looks and works a lot better...

love the CQ voice..when i hear it i can then check with a turn of the head as to who is calling

Laurie you have designed and coded a very top quality piece of software

Hey..dont tear your hair out with any problems...if we didnt make mistakes we wouldnt learn anything :-)

have a great day

73 David VK4BDJ


locked Re: Error message after saving to DXKeeper

ON2AD <on2ad@...>
 

Hello Laurie,

I use Windows 7 Professional 64 bits and my local settings are Dutch-Belgium, and my keyboard is Belgium (point) and the Ciffres are 1.000,500
one thousend comma fivehoundred.

I hope this will help to solve the problem

73 de Pat ON2AD

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

Hello Pat,

OK, looks like a syntax error in the code used to query the database to
confirm that the QSO was correctly logged. The QSO is getting logged
correctly as you discovered, it is just the confirmation message.

I suspect this is related to your Windows regional settings. Please,
what is the version of Windows and the Regional Setting?

de Laurie, VK3AMA

On 18-October-2011 02:54, ON2AD wrote:
Hello Laurie, VK3AMA

After saving QSO I become three error messages:

here the 2 (same) error message:

1. Sorry, there appears to be an error!
err.description is : Syntaxisfout (komma) in query-expressie ('Mode'= JT65') AND ('Freq'=14,07658) AND ('QSO_Begin'=CDate('2011/10/17 14:09:00'))AND('Call'='IZ5TIZ').
err.windescription:
err.number is: 80020009
err.lastsllerror is: 0
err.scriptline is: -1
err.source is: Microsoft JET Database Engine
err.helpfile is:
err.helpcontext is: 5003000

I become this message two times and then the third message is:

JT-Alert QSO log - DXKeeper (in the heading)

(Red cross) FAILURE: QSO Not logged!
The QSO Data: Callsign: IZ5TIZ - Mode JT65 - Frequency: 14,07658
Note: The QSO is still saved to the JT65-HF Log File.

But the good news is that that QSO is saved in DXKeeper
Only I become those three erro
I use Win7 Professional 64 Bits


Hope you can solve this problem Laurie

73 de Pat ON2AD

PS: sorry for my bad English and type errors





------------------------------------

Yahoo!7 Groups Links




locked Re: JT-Alert error

w7rjc
 

Hi Lautie'
In the process of getting the log file I realized that the address I put in JT-Alert was not complete I had left the last part off. Got that fixed and no more error messagees.
I have not tried to log a contact yet .. will let you know the result.
Will be gone tommorow so maybe in a day or two.
Thanks for the clue to getting rid of the error message. Ray W7RJC

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

Hi Ray,

I assume you are using the HRD5 (Access) log
Please email me direct you HRD log file that you have specified in the
JT-Alert Log File Path


de Laurie, VK3AMA

On 19-October-2011 05:21, w7rjc wrote:
Hi Laurie,

Ray W7RJC here. Well I've gotten rid of the multiple copies of JT65 v107
and have reloaded JT65 v107 and JT-Alert v1.5.0.
Now I have an error message poping up at radum.(atleast I cann't relate it to anything.) This is happening on receive.(haven;t tryed xmitt .. Yet)

This is the message ....

JT-Alert Error
Microsoft Jet Database engine cannot find the input table "Table_HRD_Contacts_V01"

error #80020009

It then asks me to make sure it exsists and the name is spelled correctly.
I did a search for "Table_HRD_Contacts_V01" and found nothing.

This error always shows up twice when it shows up.

Also the "&#92;" was already present when I went to put it in the contact window.
I have not tryed to log a file yet to see if the popups appear.

Hope you are having a good day .. Ray W7RJC


locked Re: ## IMPORTANT ## - New Fix for NOT LOGGING errors.

wd0dxd
 

Sweeet, worked for me.
 
73
KB0ASQ


locked ## IMPORTANT ## - New Fix for NOT LOGGING errors.

Laurie, VK3AMA <groups03@...>
 

### IMPORTANT ###

If QSOs are still not being logged and you are NOT getting either a "Success" or "Failure" popup window, this is most likely caused by the JT65-HF log path containing a space. This is a defect in JT-Alert 1.5.0, NOT JT65-HF.

You will need to have the jt65hf_log.adi file located in a directory path that does not contain a space.

The Fix.
  1. Stop JT-Alert.
  2. Start JT65-HF if not running.
  3. Click "Log QSO" button in JT65-HF.
  4. Use the browse button (right side of edit field) to browse to a NEW location (without a space in the path)
  5. Ensure that this new path has a Backslash "\" at the end of the path, type that character in manually.
  6. Click the "Cancel" button.
  7. Stop JT65-HF (this is important for the new change to be saved to the JT65-HF config file)
  8. Start JT65-HF
  9. Start JT-Alert
Logging should now work and a popup should appear after logging.

This fix will not be necessary once JT-Alert 1.5.1 is released (in 2 or 3 days time).

de Laurie, VK3AMA



locked Re: [Ham-Apps] Database issue

Laurie, VK3AMA <groups03@...>
 

Hi Ron,

File received, problems in db file easily identified.
I will now take this off list while we work through what may be happening.

QRX

de Laurie, VK3AMA

On 19-October-2011 04:30, Ron Brown wrote:
Hi Laurie, appreciate you looking into this I know your a busy man. Love the new version and for now I'm just importing the JT65-hf adi file for now.
All I can say is thank goodness I do backup the database, as a network administrator I'm rather paranoid about backup. I maybe the only one who has their log on a Raid 5 server, backed up to tape, copied to a different local partition, as well as archived to flash drive. Told you I was paranoid.
Anyway here is the requested database

On 17/10/2011 1:51 PM, Laurie, VK3AMA wrote:
 

Hi Ron,

This should not happen.
If your HRD log is a MSAccess .mdb file and you still have the log that
was causing the error, please email it direct to me so I can
troubleshoot what is happening.

Until the cause is found I suggest you make a backup of your log before
trying to use the JT-Alert logging.

At this point it is unclear why that error is generated. I have been
logging to HRD Access, MySQL and MSSQL logs on a local PC and over a
network to remote machines during tests and haven't seen this error. It
might be specific to your log and I will need to look at it. I will
walk-through the HRD components of my code today.

de Laurie, VK3AMA

On 18-October-2011 04:40, va7hz wrote:
> Hi Laurie and the group, the issue I'm having is abit different from some of the others. First let me say I have latest versions of JT65-HF and JT-Alert Everything except the logging to HRD is working. When I would log a QSO it would write to the JT65_log.adi file and thats it no error message, no confirmation. So I moved the log file to the C:\Temp\ directory and yes had the \ fix done previously. Now I get the confirmation that QSO was logged, but
> here is where things go downhill I go and refresh my HRD log to see it and all my qso's in the log disappear. and this is the error message I get
>
> 10:19:22 Reload Error: Getting 2987 records -
> 10:19:22 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,COL_QS L RDATE,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
> 10:19:22 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
> 10:19:22 Reload Loaded 0/2987 records in 141 miliseconds, 0.0 records per second
>
>
> Any ideas? Only way to get my log back is to recreate from backup
> Ron VA7HZ
>
>


locked Re: [Ham-Apps] JT-Alert error

Laurie, VK3AMA <groups03@...>
 

Hi Ray,

I assume you are using the HRD5 (Access) log
Please email me direct you HRD log file that you have specified in the JT-Alert Log File Path


de Laurie, VK3AMA

On 19-October-2011 05:21, w7rjc wrote:
Hi Laurie,

Ray W7RJC here. Well I've gotten rid of the multiple copies of JT65 v107
and have reloaded JT65 v107 and JT-Alert v1.5.0. 
Now I have an error message poping up at radum.(atleast I cann't relate it to anything.) This is happening on receive.(haven;t tryed xmitt .. Yet)

This is the message ....

JT-Alert Error
Microsoft Jet Database engine cannot find the input table "Table_HRD_Contacts_V01"

error #80020009

It then asks me to make sure it exsists and the name is spelled correctly.
I did a search for "Table_HRD_Contacts_V01" and found nothing.

This error always shows up twice when it shows up.

Also the "\" was already present when I went to put it in the contact window.
I have not tryed to log a file yet to see if the popups appear.

Hope you are having a good day .. Ray W7RJC