Best Way To Merge Projects Which May Later Be Separated

[rmdavidson]

I started a Data Dictionary project as a separate project in Flare because my understanding of what my boss said was that he wanted it separate. Well, apparently he wants it combined for now, but it may be separate in the future. My question is what would be the best way to combine the projects in case they do get separated later?

Right now without the Data Dictionary content our main Help is 1,700+ pages and counting. I don't know what size of a project Flare starts having fits with and the Data Dictionary may grow. Should I just do links to an external project or use Targets or should I just leave it as a separate project that doesn't interact with our main Help and just copy the topic files over or code into new topics in the main Help project leaving the Data Dictionary one intact for possible future use? If I do make it one project can/should I have multiple WebHelp and CHM Targets if we do separate things later? With all the Flare fun we've had lately with source control (and restarting Flare 3x in an hour this morning) I'm leery of doing anything without double- or triple-checking first.

Also, we use both WebHelp and CHM outputs.

Thanks,

Robin

[rmdavidson]

I stumbled on Global Project Linking after an hour or so of reading and looking through the Flare 7 online help and the forums. Should I rename my condition tags since I named them the same thing in the two different projects? Will the sets overwrite each other? The Data Dictionary set only has 4 tags, but the main Help has 12, only two of which I use in the Data Dictionary project. I don't want to lose the tags in the main Help, but am only using a tag once in the Data Dictionary so it wouldn't be hard to replace.

Thanks,

Robin

* I renamed the tags in the Data Dictionary project and it removed them from the topic I had them in rather than just renaming the tag in use like I had hoped.