|
Post by Jo on Sept 5, 2019 18:17:12 GMT -5
Robert: Your idea is nice, but I think it's rather overkill. When the CFG file is gone, what hat happend? a) the user deleted or moved the directory where the CFG file resides, including all subdirectories and \$BACKUP\s b) the network drive is unavailable or the drive letter changed In all this cases, just let the user findout what he did, you cannot help him ... Jo
|
|
|
Post by George on Sept 6, 2019 13:11:10 GMT -5
Robert: As to hoping the CFG file is not modified too often. Uh Uh, it is a very busy file, there are a lot of updates for last access timestamps. Remember all the INI's are in there, the main one and all the Profile ones.
Because all the CFG updates are atomic (i.e. user control is never returned while updates are in progress), you could use the standard SPFLite Backup as well, the CFG is just a data file.. But for comparison, how often did you (or anybody) back up the SPFLite.INI, KBD, SPS, SPR and all the Profile INIs? Mine got done daily only because I SYNC my whole \Documents folder to my LAN drive every night. I can always go back 1 day, but no more.
I agree with Jo, if it's missing, first thing is for the user to figure out why, anything else we do is pure guesswork.
George
|
|