FLDigi not uploading from QRZ, error blank, May 2017 Discussion in ' QRZ XML Logbook Data ' started by KD8M, .
KF8KI QRZ Staff EngineerQRZ HQ Staff QRZ Page Since you didn't provide the other callsign, I can't help beyond telling you that this is a problem that occurs when the user does not properly have their DX entity set in their operating location, found under settings > logbook properties. It's relatively common for things like DXpeditions and secondary callsigns where the logbook wasn't set up ...
It's not a problem, unless the logged callsign isn't in the database. When the logged callsign is in the database, if you don't provide the information, the missing data is populated from what's provided in the database by the other operator's license entry (or their logbook operating location if they are logging on QRZ).
This " that " is not a conjunction; it is a Complementizer. It introduces tensed clauses. Tensed clauses of several kinds, in fact: tensed Subject and Object complement clauses (whence the name complementizer), and restrictive relative clauses, where it may be used instead of a Wh -word. In both cases, that may be deleted if it's not needed for clarity. (there are several contexts where that ...
Do not put baluns in single element dipoles that would be used for anything other than the frequency they're cut for or the appropriate odd harmonic. Multiple-element "fan" dipoles are great with a good balun. Always use current baluns. The ONLY exception to this are the Radio Works "Remote Balun" and another 4:1 balun called the "Centaur".