开云体育

Along with the DXCC database support described below, this release also includes updated online help, which is accessible via http://www.qsl.net/dxkeeper/Help/index.htm . If you've installed DXKeeper

I should have a new version of DXKeeper ready tonite -- it doesn't use DXView during imports, and thus should eliminate the performance problem. Then we can determine whether there is an additional

Yes, multiple databases are to be avoided. I started with the notion of one DXCC database managed by DXView, with other applications invoking DXView for callsign lookups, etc. But its unacceptable for

OK, a bunch of stuff here. First I have succeeded in getting the import to work with DXView. Here is what I did: 1) Closed all applications and closed my dial up connection. 2) Disabled Norton

Wow, that is a bit complex but it sounds like you have a good handle on it. The problem of keeping two copies of a database in sync without requiring data to be entered in two places is always a bit

To ensure its ability to perform callsign lookups, DXKeeper will from now on include a copy of the DXCC database previously only packaged with DXView. During startup, DXKeeper will determine whether

The primary purpose of this release is to correct the defect in Hygain DCU rotator support reported by Julio below. I learned from Ed at DataMatrix (the developers of ProLog) that the "set bearing"

I import more than 1000 qso's from logger with out problems -----Oorspronkelijk bericht----- Verzonden: woensdag 21 maart 2001 23:50 Aan: dxlab@... Onderwerp: RE: [dxlab] Re: Progress

Our man Kurt, OE1002419, noticed that both the FR and LZ callbook URLs had changed, tracked down the new URLs, and sent them my way. So we have him to thank for the updated Pathfinder searches now

Sounds like there's a latent defect in the DDE connection between DXKeeper and DXLab. I suggest you hold off until I release a version of of DXKeeper that performs the country code lookup without

I don't know, but I am having a great deal of difficulty with the import. I took out all the DXCC entries in the ADIF file to force a lookup in DXView. It starts off going OK, pretty slow but I can

Yes, if there's a country code present in the imported QSO, DXKeeper respects it. The procedure you suggest will result in each imported callsign being checked by DXView to determine a country code.

I'm not sure if DXView was open when I did the import. However, it was open when I did the recompute. I just did that again to make sure, it didn't help. However, I just noticed something else. When I

Without seeing your log, I can't know for sure, but my suspicion is that many of your DXKeeper log entries are missing DXCC country codess -- likely because DXView was not running when these entries

Dave, When I click on a callsign in DXKeeper, obviously I have worked the guy, but the progress window does not always indicate any contact with his country. Also, I have worked 3G0Y 8 times on

I've added additional error trapping to this version -- hopefully the runtime error 6 crash W3ZJ's been experiencing will be replaced by an entry in the error log that helps me track down the root

Rich found the documentation on their web site. Given that its a DDE interface, I'll need a copy of their software for testing. It'd be best to get the software directly from the supplier -- as a

Correct And his suport are great. -----Oorspronkelijk bericht----- Verzonden: dinsdag 20 maart 2001 23:54 Aan: Dxlab Onderwerp: [dxlab] ARS rotor control Dave, Take a look at the following link

Dave, Take a look at the following link http://www.ea4tx.com/index_en.htm which is some developers information on the rotor control that Ron asked about. From what I can gather it is not an RS232

it's use the paralel port as the printer. I can send you the program -----Oorspronkelijk bericht----- Verzonden: dinsdag 20 maart 2001 22:12 Aan: dxlab@... Onderwerp: [dxlab] Re: DXKeeper