Post by Stefan on Apr 12, 2021 16:26:26 GMT -5
Some CFGMaint inconsistencies.
I thought I would 'update' and 'normalise' my CFG file with the official v2.4 Release. Hence I ran all three steps in the order shown.
-EXPORT reports "Export complete, invalid items dropped: 2" to the screen, but appears(!) to write no LOG file that tells me what was dropped.
What actually happened is that the next step (-IMPORT) occurred in the same minute and thus the -IMPORT log 'replaced' the -EXPORT log (same filename)
I know this is a rare event, but it would be handy anyway if the LOG files gave an indication of which command created them in the file name.
-IMPORT reports "19 entries corrected" to the screen. This is the LOG file CFGMaint Log 2021-04-12 21.11.TXT (5.19 KB)
Why does it 'frighten' users by reporting incorrect LASTACCESS timestamps for all file profiles?
There's nothing "wrong", except it isn't the current date/time, it never would be!
Note that it also corrected the ODEFAULT - FMLAYOUT entry, but...
1) what is "wrong" with NAME(60),LWDATETIME,SIZELONG, lines ? CFGMAINT doesn't like the 'blank' between the comma and 'lines'. FM Options accepts this.
2) why change the NAME(6) and SIZELONG as well in the correction, instead of just the one entry CFGMAINT does not like (<comma><blank>LINES)?
-REPAIR shows up a pop-up for ODEFAULT-FMLAYOUT (the 'blank' between the comma and 'lines')
shows up a pop-up for every LASTACCESS timestamp
Presumably I see these because -IMPORT didn't actually correct these entries on reload, but relies on them being fixed the next time SPFLite starts ?
I re-ran the -EXPORT against a copy of the original CFG file and learned that the 2 dropped items in the initial -Export step were:
CFGMaint - Table: ODEFAULT, Entry: $LASTPROFUPDATE=210403@13:56:26.01 is Obsolete / Invalid, Dropped
CFGMaint - Table: ODEFAULT, Entry: FMRECENTSORT=NAMEUP is Obsolete / Invalid, Dropped
CFGMaint - Table: ODEFAULT, Entry: FMRECENTSORT=NAMEUP is Obsolete / Invalid, Dropped
Both reasonable.
Lastly... OPTIONS - FM
If the FMLAYOUT entries must be specified without embedded blanks or using a particular capitalisation, the FM OPTION Panel should probably auto-correct such data input anomalies when the user clicks the <DONE> button.
