Re-Direct to Other Help Files

[Guest]

Greetings,

Our application has a static reference to one help file.

However some of our help material is dated, must be kept around, but almost certainly won't change. I'd like to encapsulate this static material into a help project, create a CHM file, compile it one last time, check it, and leave it alone.

Other material is regularly updated. I'd like to compile this material in to anothre CHM as often as is needed.

Is there a way to have something of a 'shell' help file (or other mechanism) of the file name that the application expects to be able to call, but effectively 'pipes through' help requests to one of the other help files as needed?

[JainVivek]

What is the format you have source files in?
Is Snippet in RoboHelp a good solution - define the help file as a snippet and add it in any HTML page you want?

[Guest]

For the static material I am talking about a compiled help file (CHM) with around a hundred or so topics.

I want the application calls to help to 'pipe through' to this CHM.

--- Basically I am trying to avoid having to have any material in my help system that I know will not change, but want a separate project with it around just in case something does some how manage to change.

Again the challenge is that the application only "knows" of one help file to call.

[Guest]

Looks like a "Merged Help" approach may provide the solution; will experiment and post results.