When DXKeeper uploads a QSO to QRZ, QRZ responds with a "logid", which I understood to be a unique identifier within the user's QRZ logbook. DXKeeper saves the "logid" received from QRZ in the uploaded QSO's LogID item so that when the "Sync QRZ QSLs" function later directs QRZ to report the LogIDs of confirmed QSOs, DXKeeper can quickly find and update those confirmed QSOs. I assumed that no user would ever be able to store more than 2 billion QSOs in a QRZ logbook - even DXers have to eat! - and thus made the LogID item a 32-bit number.

I recently discovered that a QRZ "logid" is a unique identifier across all QRZ logbooks. The last QSO I submitted to LotW has a "logid" of 1,112,309,417 - a little over half way through the range that DXKeeper can currently record in its 32-bit LogID items. Thus the next version of DXKeeper will expand its LogID items from a 32-bit number to a variable-length string, which can record a logid of any length.

The expansion is automatic; when the next version of DXKeeper opens a log with 32-bit LogIDs, it informs you that the log requires updating and offers to backup your log before proceeding; then it proceeds to update your log's QSOs with the expanded LogIDs.

?

Several users have already tested this automatic QRZ LogID expansion mechanism, but I would like to test the next DXKeeper version with even larger logs before making a public release. If you have a log with 50K QSOs or more that have been uploaded to QRZ, and are willing to test the automatic QRZ LogID expansion mechanism, please let me know by sending email to me via

aa6yq (at) ambersoft.com

Thanks!

????? 73,

????????????? Dave, Aa6YQ