Hi!
I wrote in very old theme "Duplicate QSL cards - identical !", that I get 8 duplicate QSL every day.
Today it was something incredible...
I have got 45 QSL, and 31 of them were duplicates of QSO that I've got yesterday !
And for example, today I got 4 QSL from SP6JIR for only 1 QSO !!! I think - it's a record of eQSL, congratulations ! :)
About the tool of deleting duplicates from OutBox - it's very interesting to read the news about new feature of eQSL, that can help in situation I have never been before, though I use eQSL almost every day. It looks like this tool was made before the problem appeared - what was before, chicken or egg? :)
But nevertheless I had to use this feature yesterday - I uploaded ONLY ONCE my file with 200 QSO and got 400 records in my OutBox. So the egg was before... proved by eQSL.
How could all that be ? How many times should I write about the problem to be listened ?
Look - it'll be just impossible to use eQSL, if everybody will have to search 1 new QSL from 30 or 40 old duplicates ! And what shall we do, when we'll have more than 100 such QSL in InBox every day ???

I just want for eQSL to be the best. For example, LoTW hides all that things from users - you cannot see what you uploaded, you cannot control the process, you cannot almost everything.... you can only hope that they really work. eQSL is quite opposite - it's opened for us. The reverse side of it - we see all the problems.
And we hope that they will be solved.
Yours,
Mike.

---

RD3AJB Mikhail Nosov

For example, today 37 new QSL arrived.
And only 4 of them were really new - 33 were already received, yesterday or ealier.
So how to find the real new QSL in that heap of old cards ??
I really don't know....

---

RD3AJB Mikhail Nosov

Still the same.... I hoped that change of servers will help somehow - no, alas, all the same... digging one new QSL in the pile-up of old....
Funny new meaning of pile-up in ham radio, tnx eQSL :)

---

RD3AJB Mikhail Nosov

I just wanted to say thanks to everybody, who repaired the soft on the server - now I see in the InBox only new eQSL ! Thanks a lot ! 73 !

---

RD3AJB Mikhail Nosov

The story returns......
Again I see undeletable QSO in my Input Box.... What is the problem with them ? Why some of input QSO remains in Input Box while many others transfers to the Archive Box after I click on them ??
I don't understand it !...

---

RD3AJB Mikhail Nosov

Mikhail,
I suggest you use th 'Help!' link above. It may take a while though. Do you know how they fixed it last time?
73

---

N1ORK Orest 'Andy' Zajac

No, I don't know how it was fixed last time... there was no reply from support.
Thanks for advice, I'll use it when it become difficult to dig up new QSL from many old ones :) Now I have only 3 "undeletable" QSL, but they have a tendency to grow, one month ago there was only one such QSL.
I am a programmer myself, so I just don't understand how this effect could be achieved :)

---

RD3AJB Mikhail Nosov

Well, the duplicates rise like mushrooms under the rain :) Now I have 7 the same QSLs each day :

EW1IP, PD1ATH, ZC4LI - old old cards that come every day for several months
HA6NL, HA6NL, M5ARC, Z37M - new old cards, fresh generation

Does anybody want them ?
I'd like to exchange them for anything else !
Prefer the DXs, of course :)

---

RD3AJB Mikhail Nosov

Thanks for the help, unknown supporter ! :) Now there are only 2 old QSL - from EW1IP and PD1ATH. I'm already used to skip them. Good work!

---

RD3AJB Mikhail Nosov

Mikhail,

I had a look at your account. You had two QSO's with EW1IP, both 30-Oct-2011, one at 03:32 and the other at 20:07. EW1IP actually sent you two eQSLs for the 20:07 QSO, so he sent you a total of three for two QSOs.

Similar deal with PD1ATH. One QSO, 12-Apr-2011, 17:54, but he sent you two eQSLs for the same QSO.

---

VA3KAB David Bell

Thank you very much, David, now it's all working good, no errors now !
About EW1IP and PD1ATH (and others I've told earlier) - I entered each of them almost every day, but they didn't disappear from InputBox... So the reason of this QSL's behaviour was that there were really entered duplicate QSL by senders... I see...
As a programmer creating software to work with SQL DB I think there might be some problem with unique number of record. In our programs we use identity field for identifying the record we are working with. It's a duplicate-proof solution - when user wants to edit or delete the record, the program get it by this identity field, not by the primary index (that can be made from call+mode+band+datetime). You see, using primary key to find the record when sender make 2 identical QSO - we'll always get THE FIRST QSO from two, and the second QSO will never be accessed this way ! :)

---

RD3AJB Mikhail Nosov

Hi Mikhail,

I can't say that was the problem with the other entries, only that the two I looked at had sent you duplicate eQSLs. There is a unique eQSL ID assigned to each record, but it is assigned when the record is uploaded, so in this case each duplicate would have a unique ID.

BTW feel free to use the support email system when you have problems, it is much better than it was a couple of months ago. You will get an answer pretty fast.

---

VA3KAB David Bell