Hi Stokley.....Not being a county hunter, I have a simple solution: only the county in which the operator is located should be counted. The car does not work anybody. Get him to move from one county to the other and work him twice.
I don't see why a logging program should have to handle this odd situation. OK, I guess I'm just an old fuddy duddy about some points of irrelevant logic. 73, Ed W1MAG ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, June 04, 2002 5:06 AM Subject: [DXBase] County lines and "Duplicate Key or Index" > Hello, > A rather common occurrence in county hunting is to work a mobile that is "on > the county line." In other words one part of the car is in one county and > the other portion is in another county...sort of a "2-for-1." Trying to log > these contacts creates a "Duplicate Key or Index" message since the callsign, > date, time, mode and band are the same although the QTH (i.e., county) is > different. In DX4WIN there is an option to specify the time in HH:MM:SS > format...by changing the time by 1 second you have "different" QSOs (and > times are listed by HH:MM). I have looked in the DXbase Help files and found > no reference to how time is entered other than HH:MM. I guess I could always > "fudge" the time by 1 minute but then the QSL label times are off and don't > reflect that a county line was worked. Suggestions? > 73 de Stokley, W3SB > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase >
