Forum Replies Created
-
Posts
-
if there is a hugher amount of entries, then I would suggest that you prepare the log with correct data and inform me when finished, then I delete the old one and you can upload the new.
In a database with 11 mio records it not like calling a record, enter new and thats too time consuming.
on what basis you are doing the updates ?
DL2ND and DL2NO are both active DLFF-hunter.
If you change it to DL2NO, then you take the point away from DL2ND, are you aware of this and did you reconfirm with DL2ND??
changes doneunbelievable, there were in altogether 135 log-entries the call wrong written as K04SB instead of KO4SB.
I´ve updated all. 73the logs 67031,67032,67033 were updated, however there is an additional log for KFF-3671 and KK1TLS also from 2019-01-12 uploaded by you with another 20 contacts, is that correct too?
Hi, I already answered this in the mail you´ve sent me, sent you also a listing with all listed contacts:
Hello Victor,
attached you find a listing which logs from UNFF are in the database.
As you see, your UP44WFF-logs should be there.As Andrew already explained you some days ago there is still a problem with the clubstation-statistic.
The Top-Operator-Statistic is coming from the operator-call in your log.If you look and try to find for example DA0CW/p then you find also nothing, as DA0CW/p is our club-station and currently doesn´t appear in the club-overview,
(but still made around 25000 QSO)If your logs would contain the operator-callsign, then it would appear in the top-operator-statistic, but they didn´t contain this field.
So anyhow you have to wait until Andrew fixes the issue with the clubcallsign, so don´t worry the contacts are there and credited to the stations you worked.If the list of logs are not complete then please contact UN7GIT, as you see I did the uploads before UN6QC started and turned later to UN7GIT.
If there is something missing, then he needs to load it up.73, Manfred DF6EX
