That is how I do it.

In reality it is little different that working different portable locations.

N3FJP AC-Log will receive input and store any information you put into it.  For example, I maintain a log for USA operations, and it contains log entries from the states of TX, OK, AR, NM, MO, CO, AZ, WY and CA.  I use one of the OTHER fields to annotate what my portable locations were.

I maintain a second log for my operations in Europe.  That log contains portable operations from DL, HB9, HB0, OE and OK, and the DL portion is made up of some greater number of portable locations, probably 2 or 3 dozen total.

Where it becomes tricky is when uploading to on-line QSL services.  I will use LoTW as an example.  When I operated as HB0/KD5KC, to upload it to LoTW *PROPERLY*, I had to be certain I requested a call sign certificate from ARRL denoting HB0/KD5KC, with the proper start date.  When I used that certificate in T-QSL, I needed to be certain that I had the proper IARU and CQ zones included, and the proper grid in the station location file I built for that operation.  That way any confirmation would show me in HB0, not DL or TX etc.

As I operate portable a lot, I am quite careful to make a new location if anything at all changed.  I upload 6-digit grids. And if I move from DM61st to DM61su, I will build a new station location.  It would be perfectly legal and proper to just log it all as DM61 in the proper state and county, and call it good.  Kind of up to the user what level of detail they like.  I enjoy VHF/UHF and some appreciate the greater detail of a 6-digit grid.

Hope you find this useful.  As long as you get the info correct, it is pretty well up to you.

Mike – KD5KC -- El Paso -- Texas.

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

ADVENTURE:  The respectful pursuit of trouble.