XMLog 7.01 Date Change

I've changed the way 2-digit years are handled. It turns out that long ago I decided that when you enter a 2-digit year (as part of mm/dd/yy) and "yy" was less than 20 XMLog would assume that you meant 20xx and if "yy" was greater or equal to 20 then it assumed you meant 19xx. At the time this seemed like a good idea because you were not likely to have any QSOs before 1920 and 2020 was 40+ years in the future. 
However, someone recently pointed out that a log search using a Date field of <01/01/20 was not working and it turns out this was because XMLog was treating this value as <01/01/1920 and not <01/01/2020. 
I'm glad that this was discovered with almost a year to do something about it because when 2020 comes around and you enter a QSO date like 01/03/20 this QSO will actually be stored in your log as 01/03/1920. 
Version 7.01 will change the "break point" for the century from 1920 to 1930. This means that any dates with "yy" values of 30 or more will be treated as 19xx and any dates with "yy" values less than 30 will be treated as 20xx. 
This means that you need to update to version 7.01 before December 31, 2020 or those 2020 QSOs will get stored as 1920. 
I'm sure some XMLog users will not hear about this update and wind up with some 2020 QSO dates that are saved as 1920 instead of 2020. To deal with this problem of "late" updates Version 7.01 will check log files for dates less than 1930 and boost them by 100 years. This check/update is only done the first time a log is opened. 
Note that these comments also apply to the other date fields in a log entry: QSLSent/Rcvd, LoTWSent/Rcvd, eQSLSent/Rcvd, and DXCC/WAS/WAZ Submit/Accept/Reject.