Hi Fred I think that the concept of the OPR Call field is that it should allow anyone visiting the shack to operate and for the registered owner to know who it was, not enforcing the call against the registration. So the concept that it should be a registered call is not how I understand the use of it.
The other two points, however, do not appear to live up to the purpose of the field (it should not be part of ADIF export validation). The DXBase re-write will only use a registration key for installation and not for operational verification BTW. I will see if there is an easy way to fix the opr call validation 'bug' in the current version! 73 Neal Campbell Abroham Neal Software www.abrohamnealsoftware.com (540) 645 5394 NEW PHONE NUMBER Amateur Radio: K3NC Blog: http://www.abrohamnealsoftware.com/blog/ DXBase bug reports: email to [email protected] Abroham Neal forums: http:/www.abrohamnealsoftware.com/community/ On Sat, Feb 19, 2011 at 3:36 AM, Fred Handscombe <[email protected]>wrote: > Hi Joe > > I want to add my thanks fo the support you give the DXbase users! > > I have a suggestion for a new report or utility. > > DXBase uses the "Opr Call" column to "validate" the use of the programme. > I > have had many discussions with Jack over the years as to why this is wrong > under the licencing conditions in some countries and hopefully something > new > will be used under the new ownership/SW release. > > The way the OPR call column is used introduces errors into the logs and the > way they interact with the likes of Club Log and LOTW. In fact it was > using > Club log I have spotted my problem (check it out and join at for free > www.clublog.org ) > > First the Opr Cal is NOT validated against the valid registered callsigns > which it should be. You can enter anything in the column and you are NOT > warned, which seems a little unwise when the column is used later to > "validate " the data. > > Second if the Opr call entry is NOT one of the registered callsigns then if > you do an ADIF export to LOTW, for example, then that line of data is NOT > included in the export file. > > Third if you do an LOTW export and certain lines are excluded, these line > ARE marked as sent to LOTW even though THEY HAVE NOT BEEN sent!! How crazy > is that? Maybe you see my disagreemnet with this "method" of validating > the > user. > > So Joe my request is a report or utility that checks each log line for a > valid registered call against the registration file, and flags up any wrong > entries in Opr Call column. If there was a way to open each entry for > editing, to undo the errors introduced as above, or do it automatically, > that would be even better > > 73 Fred > G4BWP - A65BD > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
