by Rob_S » Sat Jul 23, 2022 2:45 pm
I agree with that, and in spite of some confusion in my earlier postings, it seems to me autobackup should be enabled by default, and I also think the backups should appear somewhere people who do not have "show hidden files" enabled can still find them. Maybe a setting that must be chosen upon installation??
Can anyone who has had autobackup enabled confirm that it actually produced a series of dated .db files, contrary to OP post above??
Also, can anyone confirm if the original database does become corrupted, will the program offer to reload last previous backup, from users designated backup path?
Backups are important, particularly since the database contains basically all the "work and effort" the user has put into this program, and knowing that it can become irretrievably corrupted.
I think for some reason peke above was thinking of backing up his Library of tracks, which is a whole separate issue. It would not be unreasonable for the program to have such a feature built into it.
I agree with that, and in spite of some confusion in my earlier postings, it seems to me autobackup should be enabled by default, and I also think the backups should appear somewhere people who do not have "show hidden files" enabled can still find them. Maybe a setting that must be chosen upon installation??
Can anyone who has had autobackup enabled confirm that it actually produced a series of dated .db files, contrary to OP post above??
Also, can anyone confirm if the original database does become corrupted, will the program offer to reload last previous backup, from users designated backup path?
Backups are important, particularly since the database contains basically all the "work and effort" the user has put into this program, and knowing that it can become irretrievably corrupted.
I think for some reason peke above was thinking of backing up his Library of tracks, which is a whole separate issue. It would not be unreasonable for the program to have such a feature built into it.