wellread1

If the native KeePass 2.x Repair Mode returned an empty folder then nothing could be recovered by KeePass. You can check the size of the database on disk. If it is zero or significantly smaller than the original or recent backup the corruption is profound. Regardless of the database current size, there is nothing to be done if Repair mode failed. Since you are not using KeePass it is difficult to suggest a course of action however if you are saving your database to a cloud service then there may...

…find a combination that took the field to select the Release option I am not certain what the above clause means, but I think you are trying to export selected entries across multiple groups and include the group hierarchy in the exported file. Make sure that View>Show Entries of Subgroups is checked and View>Grouping in Entry List is set to ON or Automatic. Select the highest parent group that contains entries that you want to export. Then use the Entry pane: In the Entry View pane select the entries...

…find a combination that took the field to select the Release option I am not certain what the above clause means, but I think you are trying to export selected entries across multiple groups and include the group hierarchy in the exported file. Make sure that View>Show Entries of Subgroups is checked and View>Grouping in Entry List is set to ON or Automatic. Select the highest parent group that contains entries that you want to export. Then use the Entry pane: In the Entry View pane select the entries...

…find a combination that took the field to select the Release option I am not certain what the above clause means, but I think you are trying to export selected entries across multiple groups and include the group hierarchy in the exported file. Make sure that View>Show Entries of Subgroups is checked and View>Grouping in Entry List is set to ON or Automatic. Select the highest parent group that contains entries that you want to export. Then use the Entry pane: In the Entry View pane select the entries...

I have not thought about or used this trigger set in years, and it would take more effort than I am prepared to make to re-familiarize myself with the details. This is especially true with regard to any limitations or behavior details that are not already covered in this thread. My personal opinion is that this syncing scheme is not very scalable, and it is hard to maintain. For most situations it will be simpler and more practical to create entirely separate databases having non-overlapping contents...

KeePass doesn't support separate "identities" in the same database, e.g. children's identities. These suggestions would require major changes to the KeePass database that are unlikely to be implemented. The extra complexity of supporting separate user identities in the same database, e.g. user-level access rights, are more appropriate for enterprise-level password managers. If you need separate user identities, create a separate database for each user. KeePass can open databases concurrently in the...

KeePass doesn't support separate "identities" in the same database, e.g. children's. These suggestions would require major changes to the KeePass database that are unlikely to be implemented. The extra complexity of supporting separate user identities in the same database, e.g. user-level access rights, are more appropriate for enterprise-level password managers. If you need separate user identities, create a separate database for each user. KeePass can open databases concurrently in the same workspace,...

KeePass doesn't support separate "identities" in the same database, e.g. children's. These suggestions would require major changes to the KeePass database that are unlikely to be implemented. The extra complexity of supporting separate user identities in the same database, e.g. user-level access rights, are more appropriate for enterprise-level password managers. If you need separate user identities, create a separate database for each user. KeePass can open databases concurrently in the same workspace,...