Hi John, I ran 1.4.1 yesterday and can confirm the setting was indeed in that version. I am not sure why I didn't migrate that setting to 1.5.0 as I would only have added the feature initially as the

Hi John, That email address is OK, just now tested. I can't locate a one month old message from you. Please send again. It is OK to post to this group, and html messages sent from an email client

Hi David, I'll walk through my code today. Not sure why the quote is missing around Mode. I personally use DXKeeper logging and I am surprised that it can be broken by the missing quote

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

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

The only way to post a screen-capture is to use an email client and format the message in html and include the image in your email. Unfortunately if posting via the web this cant be done. There is a

Laurie -- looks like missing quote around the JT65 string value ... Are those single quotes (as opposed to something different than the string literal quoting) around the column names correct? What's

Hi Laurie. Sorry for putting the message here but I'm not sure how else to contact you! Just over a month ago I sent in a problem report for Hamspots complete with a screenshot. Did you get it & or

How do you add an attachment to a post? I want to add a screen shot. 73, KJ1J

Hi de Laurie and Scott also Thanks for the reply to my trouble with loginng records to HRD logger. AS was suggested I checked out what method I was (am) using. It is the HRD V5 (access). I have set

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

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

This is going to be an option correct and not a full functional change to how B4's are handled? If I've worked John WA3CAS on 20m, but now operating on 40m and see him calling CQ I only want to see

Hi Laurie, That's exactly what I want to see happen. I want to see "B4" appear next to the call no matter what band I worked him on. I swear that feature was already available in v1.4.1. For me, it

Ray, I'm using Win7 myself, and the path I needed to put in was this: C:\Users\owner\AppData\Roaming\Simon Brown, HB9DRV\HRD Logbook\HRD My Logbook.mdb I don't know if

Hi Ray, You should get a popup window after logging, advising either success or failure. If you are not getting any popup, then it sounds like you don't have the correct path set for the Log file, or

Hi all, I have tryed most of the afternoon to get JT-Alert to work with HRD logger .. to no avail. I don't even get any nasty grams. I have done the \ thing in JT65 as suggested. Perhaps I don't

Hi John, So what you want is... say you have worked VK3AMA only on 20M, you are currently on 10M, VK3AMA is decoded on 10M calling CQ, you want that decode to show as a B4. Is that correct? If so, it

Hi Laurie, B4 alerts for stations worked on the current band is working great, but stations worked on other bands are not being flagged as worked B4. There's a note in the Worked B4 configuration

Good to hear Larry. I'm missing all the 10M action (actually every band except 30m) as my SteppIR is off the tower on the ground in preparation for a new SteppIR arriving next week. Early Christmas