Patrick

Yes, thank you. All databases are in the same directory stored in my cloud, I simply can duplicate and rename it. But anyway, if there would be an option in the future that would be great. TBH I always wondered why my databases were messed up and restored history entries, even when I deleted them. Wasted a lot of effort into this manual maintenance. On second thought - maybe another proposal: Could there be a flag (Checkbox, Tag) to have a "locked history" for certain entries, so if I clear the database...

Could you let the user decide if they want to merge or remove deleted history entries? I've created the multi-way-sync to make my database(s) less volatile and I want to mirror my databases. In case of multiple edits (e.g. on the desktop (while offline) and on the phone (on the go, online)) the entries should be synced. Otherwise I could create a simple one-way sync (which is not possible with KeePass but the cloud), but I would risk loosing data. Thanks and best regards, Patrick

I have to make a correction to your post: Initial state: Identical copies of entry A are present in both db P and S. State before synchronization: Entry A is edited in S. History of entry A is deleted in S. State after synchronization: The full entry history of entry A (re)appears in database S. The complete entry history will also appear in P. There is an additional history entry in both P and S on top of the existing history.

Entry history get's restored (and there is added one additional entry) on DB sync

Hi, thanks for your reply, but I want to keep the history, but sometimes I want to delete certain history entries, to keep my database lean. I did set up the multi-way sync not to have any file conflicts anymore. I honestly think that's a bug anyway, since I tested it now with 2 new DB's and if I delete in DB1 the history (trigger on save) I get the history back +1. So if I had 1 history entry, tried to delete that, it was restored and further there is an additional history entry, so I end up with...

Hi, I set up my databases as primary/secondary since I ran into sync problems in the past. I followed the instructions here https://keepass.info/help/v2/sync.html and here https://keepass.info/help/kb/trigger_examples.html#dbsync My problem now is: When I edit the history of an entry in any DB, for example delete all old history entries, they get restored on sync. I set up triggers to sync on Open and Save. I also tried to delete the history entries in the primary DB, saving and opening the secondary...

I think it would be great if one can change directly the string-field fonts, without additional addons like KPEnhancedEntryView.

+1