Link to projects w/small TOCs and not get duplicate topics?

[amatsumoto]

I have built WebHelp output before where the main project has a TOC with links to sub projects and it creates one big, happy help build, but I am trying to do a variation of that and have run into a snag. In the past, the links to the sub projects were always to just one sub project TOC. So, for example, if I had a project that contained hundreds of topics on commands, the final help build would have a single TOC entry for all of the command topics coming from that separate project.

What I want to do now is blend some of the TOC entries in the final help build regardless of whether the topics come from the main project or a sub project. For example, if I have a TOC "book" set up for workflows, the setup in the main project's TOC would look like the following:

Workflows
Link to topic from main project
Link to topic from main project
Link to small TOC in sub project that contains five sub project topics

and I would expect the help output TOC to look like this:

Workflows
Topic from main project
Topic from main project
Topic from sub project
Topic from sub project
Topic from sub project
Topic from sub project
Topic from sub project

I know that I can achieve that part of it and I want to create at least 6 or 7 of these small TOCs in one sub project (it has thousands of topics), which means there will be 6 or 7 links to those different small TOCs in the main project. It's simple to create those little TOCs, but the BIG problem is that my help build will have duplicates of every single topic coming from the sub project, 1 copy for each TOC I link to. Flare is generating the full sub project help for the for each TOC I create and each of those copies is being placed in its own output sub directory. While I won't see duplicate topics in the help TOC tree, all I have to do is go to Search or the Index and type in a keyword and there I will get 6 or 7 duplicate topics listed for every single topic coming from the sub project (since Flare generates the help topics whether you include them in a specific TOC or not). Here is an example of what my output directory would look like if I had 6 small TOCs from one sub project, if that helps:

ACMEWebHelp
\Content (contains topics from main project)
\Data
\Skin
\Subsystems (contains output from sub project)
\Output from sub project mini TOC 1 (contains all topics from sub project)
\Output from sub project mini TOC 2 (contains all topics from sub project)
\Output from sub project mini TOC 3 (contains all topics from sub project)
\Output from sub project mini TOC 4 (contains all topics from sub project)
\Output from sub project mini TOC 5 (contains all topics from sub project)
\Output from sub project mini TOC 6 (contains all topics from sub project)

This is why Search would find 6 matches to the same topic if it was a topic from the sub project.

Is there any way to prevent the duplicates? I know I can move the sub project topics permanently into the main project and it won't be a problem anymore, but for a multitude of reasons it is not a desirable solution. I also know that I can trick this into working if I apply conditional text to every single file in the sub project and generate every single TOC using the correct conditional text settings for output. Also not a desirable thing to have to create and apply 6 different conditional text tags to thousands of files if I can avoid it.

Any other suggestions, or are the above solutions my only choices?

Thanks!