I just found our from Korm that replicating across databases is impossible in DT.
My suggestion for future DT updates is content replication across databases, even closed ones. Treat databases like folders, where you can send an alias to even a closed folder.
I’m not coming outta right filed with this, am I?
I’m not sure how that would work. A replicant is an exact copy, so any changes are made to all copies. If changes are made to a replicant in an open database, and a replicant exists in a closed database, how would the changes be handled? That makes my head hurt. 
Cheers,
Karen,
OK. I get it now. Thanx.
…but…
Not to muddy my own water, but it’s possible to index a file that is inside another database. Like, if in database B you index MyFile that’s inside database A. (There’s a technique to do this using temporary aliases - this is scriptable.) The net result is that you’ve rolled your own inter-database replicant - with no guarantee of course that the links between these files will always work.
In that case I’d suggest to store the file in a folder and to index this folder to both databases. Indexed files are editable too since v2.
That’s the second time I got this tip: I’d better remember.
Thanx, fellas.