 |
|
eQSL.cc Home
Search
Login
Authors
Recent Posts| Viewing User Profile for: G0NUP Kevin | |||||||||||||
| About | Contact | ||||||||||||
|
Send Private Message |
||||||||||||
| Post Statistics | |||||||||||||
|
G0NUP Kevin has contributed to 3 posts out of 11719 total posts
(0.03%) in 8,724 days (0.00 posts per day).
20 Most recent posts:
Support - English speaking »
Handling /P callsigns becoming a problem Jul 15, 2010 06:57 PM
(Total replies: 5)
Hi Doug, thanks for the reply. Well I think the point I'm making is that most logging programs nowadays will allow you to 'change operator' which in turn will allow you to output a list of contacts based on the operator. Which I do for special events. However, I can't understand why eQSL does not treat G0NUP the same as G0NUP/P. With ref to SOTA, adding the location that was used in the 'comments' field. This would mean that all G0NUP , G0NUP/P , G0NUP/M would all be in the log, after all the operator is the same and all his details (personal) are the same. The difference would be highlighted in the comments field. Along the same lines when I operate as 5B4/G0NUP (5B/G0NUP) my log is now different as I'm 5B so this justifies a separate log database as it would if I was GW0NUP/P whilst in Wales. This would also reduce the number of individual databases on the eQSL system., As a programmer, I can't see the difficulty in filtering the /P or /M off either side of a QSO and keeping a single logbook.?? Just thoughts for open discussion. 73 de Kevin G0NUP Kevin
Support - English speaking »
Handling /P callsigns becoming a problem Jul 13, 2010 04:46 PM
(Total replies: 5)
Hi I am a SOTA chaser (Summits On The Air). as such I keep a log, using Logger32 which is quite flexible. I upload on a fairly regular basis into eQSL I have a problem however. SOTA activators (not all) when they are activating a summit use their call with a /p. However when they are entering their data into the eQSL database they are omitting the /P for ease of entry....? (some do it correctly) This in turn has a major problem on my INBOX, it show the normal stations worked, but almost all the SOTA callsigns who do not use the /P have the big red X and the green tick. This means a whole load of additional work for me, and additional load on the database. Now surely if a station is LLFLLL he is the same operator as LLFLLL/P only working from a different QTH. (LLFLLL letter Letter Figurel, letter,letter letter example only, others do exist hi hi) All his/her details will be the same other than QTH. What thoughts are there on this subject? Are there any moves afoot to sort it out? Regards 73 Kevin G0NUP G0NUP Kevin
Support - English speaking »
Delete incorrect mode entries Jun 17, 2009 08:43 PM
(Total replies: 0)
Hi all, I have, sometime ago, created myself a problem which I had forgotten about. Somehow, I entered a series of QSO's with an incorrect mode in PSK, should have been PSK31 However using a different logging program I also uploaded the same log with the correct mode PSK31, I now have loads of entries in . RED I know I can do the delete a record at a time. But is there a way of doing it enbloc....? Added information is that some of the correct entries have been used by other users. So I assume I can't delete a whole block??? 73 de Kevin G0NUP Kevin |
|||||||||||||