I think I have a simpler solution, although I haven't tried this yet. It's just
off the top of my head, so forgive me if it's hairbrained...
Why couldn't you put the shared field "ResourcesRepID" in the resources.nsf,
and set resources.nsf to be a template, and then let all the other dbs inherit
the changes of the shared "ResourcesRepID" field. I assume the resources.nsf
db could calculate it's own replica ID?
Because design elements refer to templates by name (without any path), every
database would get the shared field, which would have the correct replica id
all the time, even if you replicated or copied all the databases to a new
server or whatever.
(as far as an .nSf being a template, I'm quite sure I've done this without any
problem.)
Please tell me if I'm mistaken about this working...
I think I have a simpler solution, although I haven't tried this yet. It's just off the top of my head, so forgive me if it's hairbrained...
Why couldn't you put the shared field "ResourcesRepID" in the resources.nsf, and set resources.nsf to be a template, and then let all the other dbs inherit the changes of the shared "ResourcesRepID" field. I assume the resources.nsf db could calculate it's own replica ID?
Because design elements refer to templates by name (without any path), every database would get the shared field, which would have the correct replica id all the time, even if you replicated or copied all the databases to a new server or whatever.
(as far as an .nSf being a template, I'm quite sure I've done this without any problem.)
Please tell me if I'm mistaken about this working...