I have two main QTH's, plus 2 shorter term less frequent, plus an RV doing Mobil.
Should I setup 2 or 4 or 5 accounts?

If I have multiple, all attached, can I then go back and change the dates on them to show where I am active, and not loose ability to go back to the original?

Or would I have to setup new accounts for the same old locations when I go there?

Sort of an expanded vacation home situation.

---

KE7RG Robert H Galyan
Edited by F6DKQ Guy FALCOZ on Nov 13, 2019 at 12:32 PM

We in the UK by the way our callsigns are organised need quite a lot
My call can be
G0CER, GM0CER, GW0CER, GI0CER
also
G0CER/M G0CER/P G0CER/A and all the above variations can have the /M /A /P
For historical calls there are even more GQ0CER, GV0CER and other special prefixes.

I know its way too far down the line to change but if an account were to be separated into:

- Country Pre prefix - a country I may visit under CEPT rules [W4/G0CER for example])
- prefixes (in my case potential ones are G, GW, GM, GI... etc)
- suffix My call 0CER that doesn't change
- extensions /p /m /a .... etc (& RV )
- Post country add-on Where required say G0CER/W4

My account could be just one then, with programming separating what QSO join up with what unified call I was using. (as long as I told it!).

Dave G0CER, G0C (short contest call!) and KJ4QAO

---

G0CER Dave Harris

The rule is simple : you cannot have several accounts for the SAME callsign with OVERLAPPING dates

Knowing this, you have eventually to create multiple accounts if you go back and forth

The mobile question is different : you will use KE7RG/m........anyway but there again, you should create as many accounts as different grid squares, counties if you want them to count for Awards.
We don't have solutions so far for highly mobile stations

If you have 4 different locations, you have to set 4 accounts, yes. No you can't change the dates now and then, If you can, name your other locations another way /0,1,.....9. or /a or /p....etc
Thus, you could set a long date-range for each account....or else, you would have to create a new account each time to move from a location to the other.

NOTE : If you create several accounts, beware to log into the right account when you upload QSO's !!!!!


73, Guy F6DKQ

Years ago, you required me to create overlapping accounts, but now that you have restricted them from being overlapping, my accounts are all screwed up and cannot be corrected.

I have over a dozen things I need your staff to do to fix my accounts.

---

N4PGW Buck McDaniel

I'm fully aware of the situation with regard to highly mobile stations, as well as users who have a vacation home they visit often, or an office with a rig, or other situations where you are operating with the same callsign from several different grid squares, or counties.

While we do have MS SQL Server, a relational database, that is in fact more of a problem than a solution. In the olden days of flat files, we would just store all the QTH data in each log record and be done with it. But since the QTH implies not just a 6 character Grid Square, but also a County, and a Country, and State, and Lat/Lon, and the entire definition of the eQSL graphic and layout, and the awards earned from that QTH, you can see how such a database would rapidly get astronomically huge.

The relational database SQL Server is good at fixing the issues of repetitive data, but eQSL.cc is both an OLTP as well as an OLAP type of system. That is, we have transactional data that requires rapid response (you don't want to wait 10 minutes to display one eQSL or to upload one record), and also requires the ability to process mountains of data quickly to see what eAwards a user has earned, to create the Propagation Forecaster map, to display the Satellite Status screen, and to look at Inbox and Outbox data for very large users.

So, we have tried to create a balance between OLAP and OLTP. And to do it without the kind of "batch processing" that LOTW requires. When you upload a log record, that eQSL is pretty much instantly available to the user at the other end. I've worked many stations now on FT-8 where I could pull up their eQSL before I had even finished sending my 73!

I have been intensely working on a solution to this for several months now, and have been pondering it for almost a decade. In my mind, the only viable solution is one in which a mobile station can upload all his logs, while enroute, and if there is no Profile record currently available for the QTHes of his grid squares, it will put them into an "On Hold" screen, where he can sort them out after he gets parked and has a few minutes to decide, did he set his QTH incorrectly and they should go into one of his existing accounts? Should the system automatically generate a new QTH account and copy over his eQSL graphic design and put the new records there? What should be done? He will have a set of buttons at the bottom of the screen to dispose of any such records in the On Hold Box.

My acid test case for this is when I go flying in my airplane and work a bunch of stations while flying at 170mph across the country. I want my logger to automatically store the lat/long and the grid square I'm in, and I want to upload everything in real time, or after I land, and then sort out anything that doesn't have a place to go.

To do so will also require creating a single User-level login that will consolidate all of what we currently call an "attached account" into something more like a "QTH profile". Each user could then have as many QTH profiles as necessary, with a single screen to manage them all, find orphan eQSLs and move them, etc. Much like the "Experimental Account Manager" hidden away at the bottom of the "My Other Accounts" screen.

I have been working on the User-level code for over a year now.

So, while it may appear that we "don't care" about mobile or portable stations, I have 2 avid county hunters on the Advisory Board, as well as one big gun DXer with a lot of DXpeditions under his belt, and I am constantly encouraged to work faster on all this! LOL

(See you on the satellites and 20m FT-8)

---

Of course, that's just my opinion... I could be wrong!

73,
Dave Morris, N5UP

I want to make sure I have this straight. During my November vacation I activated 6 parks here in Texas. None were in my home grid. I did an upload and all 525 contacts were rejected. SO...I will have to add 6 more call signs and upload each log by it self for each location? So, when in 2021 I activate, say, another 20 parks,I have to add 20 more call signs?
Is this the correct answer?
Ray.
WR5AY.

---

WR5AY Ray Luedecke

Yes, it is

Many SOTA activators have dozens of accounts

not necessarily CALLSIGNS, you can have a single /p callsign with many accounts, each with it's own date-range

not really rejected....flagged in red as questionable because the datas you upload don't match the settings of your account profile

---

73 - F6DKQ




Edited by F6DKQ Guy FALCOZ on Dec 16, 2020 at 06:48 PM

If you add the accounts by going to My Accounts -> My Other Accounts, at the bottom of the page you can "Add a new Attached Account", and it will copy over most of the information so all you are doing is changing the QTH.

This gives you the ability to have a different QSL design for each QTH, if you wanted to do that. And it makes sure that all your eQSLs are valid for credit to the recipients for their use in eAwards.

---

Of course, that's just my opinion... I could be wrong!

73,
Dave Morris, N5UP

If I may add my 2 cents worth - I don't mind if an eQSL record of a QSO only becomes available after some processing time, even if it takes a day or two. I also don't mind having multiple accounts for every callsign and fixed QTH that I have had. But I would find it rather inconvenient to have many different accounts for my portable operations, some of them perhaps even split into multiple parts because I worked from one place first and returned to it only after making some QSOs from other places. It becomes even more awkward if I only made a small number of contacts from some of these places. Regrettably, I had to reject a few dozens of eQSL requests for that reason.

My preferred solution would be to make the QTH and associated information an array of variables (containing e.g. place name, Locator, administrative unit, IOTA number) that can be defined by the user and stored en bloc in some sort of menu, from which I could select one for each entry. Not sure how that would work with the current structure of the database, though.

---

M0CEF Jan-Martin Hertzsch

So I have an account for my Home from 12-28-2021 - 12/31/2029

I tried adding an account for my home POTA park since it is not in the same grid as my home anymore since I moved. I get a message about overlapping dates. Of course they will be overlapping. How can I get around this issue?

---

N1RBD Richard B Dervan

Hi Richard,

I think you should set 'Callsign / QTH End Date' in ’My Profile’ to the date you moved.
Good Luck!

JJ1SWI/Gou

---

JJ1SWI/1 Gou Kagawa