开云体育

I am trying to wrap up the next release 5.02.02 of the logger and need a couple of more beta testers tht are available to help. If interested please respond offline. Summary of changes to this

Dean, Morning, I reloaded the program, left the computer off for 4 days and low and behold last night it launched. I put the new backup file from my other computer in and it seems to be working just

Sure thing, Dean. Thanks. RJ, NA0L --In N7XGlogsupport@..., <dean@...> wrote : RJ, Rick, OK, dug deeper and found the problem. I will get it corrected in 5.02.02. RJ, when I get the beta

RJ, Rick, OK, dug deeper and found the problem. I will get it corrected in 5.02.02. RJ, when I get the beta ready could you do some testing for me? Dean Davis, N7XG

Rick, Are you sure you got only 7000 and not the full 17000, or some other number? We may not be talking about the same thing. I am not saying that ADIF export fails, but that, for example, if I

My initial testing shows it doesn't work with 14c, but works with 5.02.01 where I exported around 7000 filtered records from my log of 17000 entries.

Thanks, Dean. I discovered some more info. I thought it might be a size related problem as I have 13,000 records in my database. I restored some old backups and found that for 2200 and fewer records

RJ, OK I will look at it again and get it fixed in 5.02.02 Dean Davis, N7XG

OK, I guess it's just me. It has conistently failed to work across three versions and four machines. As I said, csv export works fine with a filter. I will try to create a simple db that exhibits the

I just got a brand new Windows 10 computer and the logger works perfectly for me. KM9U

Dwight, This is a file permission problem on your Win machine. Try running ad administrator. If this does not work give me a call. Dean Davis, N7XG

I suppose what I need to do is not export the state field and figure out how the ADIF specification wants it. Dean Davis, N7XG

RJ, In any version of the logger you can filter data and export. Dean Davis, N7XG

Dean, That was me. Even if I filter down to a handful of contacts, ADIF always exports the entire database. This is still true in 5.02.01. CSV export works as it should. RJ, NA0L ---In

Dean Davis wrote: Another question arose about DX, specifically Canada. How should these be reported in ADIF. ----------- The ADIF people apparently are deprecating VE_PROV in favor of two-letter

Dean, Any input on the emails from yesterday. When I try to launch the program with windows 10 it won't be past the logo page and says the program has stopped working. If you can give me some info

Dean For Canada, a US op is supposed to sign as Call/Canadian identifier, e.g., KI4WCQ/VE3. I think that is the way the call should be entered under call in a logger. Most of the time one would see

Johnny, I think in an earlier post you expressed a desire to be more selective when you do ADIF exports. In the current version on the main menu you can filter contacts and when you do an ADIF export

What I have seen in the past were things like this: VE3/W1ABC or W1ABC/VE3 What I will add is a second check ox to append the /P and hopefully people can figure it out for them selves. Dean Davis,

I see the problem a P5 would cause, but you can't account for all cases of stupidity or ignorance by an operator. I would simply offer the option of /P. If it is something more unusual such as /call