I love the Replicate feature, it allows me to avoid the dilemma of the century of whether to use groups or tags.
The only concern is that when one of the replicated files is moved from database A to database B, the other replicated file in database A will be deleted as a result of the operation.（I want to keep files in both database A and database B, even if Replicate no longer works）
There are two solutions I can think of.
Use Duplicate: Generate a large number of redundant files and cannot be modified synchronously.
Avoid moving files to another database: I tried to reduce the chance of this happening, but I don’t think it can be avoided 100%.
I’m in a struggle, do you guys have any good suggestions?
No, there’s no other solution.
You can’t replicate across databases.
If you find yourself wanting to replicate between databases often, perhaps you should stop and rethink your database organization.
Perhaps you have created database that are too specific(though I think too specific is better than too general).
Perhaps you need to create a library database that would house this common information.
Perhaps tags and smart groups are a better option.
Perhaps you are trying to create too many instances of files via replication, creating replicants that seem right in the moment but aren’t truly useful in the long run.
