.CHM from a Converted Flare Project Doesn't Launch

[amyrn]

The Issue:
I am working on a Help file that was converted from RoboHelp to Flare. Our QA is attempting to launch the Flare-generated .chm by clicking the Help button from within our application. QA says the Flare-generated .chm does not launch. (When I attempt to launch the .chm, I receive this error: HH_HELP_CONTEXT called without a [MAP] section.) However, the .chm that RoboHelp generated does launch, without any errors.

The Details:
The new Flare project contains context-sensitive IDs, that are the same IDs used in the RoboHelp Help. I also verified the IDs in the .hh file. I am running XP.

Thanks for your help.

[Pete Lees]

Hi, amyrn,

As well as the map (.h) file, do you have an alias file that links the topic IDs to the target topic files? The context integers that an application passes to the help file must be mapped to topic IDs, which in turn must be aliased to the topic files.

See:

About Alias Files
About Context-Sensitive Help

Pete

[amyrn]

Thanks for your response. I do have a .flali alias file in my project. I also double-checked my .hh file against the .flali file, to make sure the context IDs match.

[Pete Lees]

Hi,

Do you get any error messages when you compile?

You'll receive the "HH_HELP_CONTEXT called without a [MAP] section" message when opening the .chm file if every topic ID is aliased to a topic file to which you've appended a bookmark, like this:

Code: Select all

IDH_Start = Sample.htm#Start
IDH_Middle = Sample.htm#Middle
IDH_End = Sample.htm#End

if this is true in your case, the solution is to add another alias that doesn't contain a bookmark. For example:

Code: Select all

IDH_Sample = Sample.htm
IDH_Start = Sample.htm#Start
IDH_Middle = Sample.htm#Middle
IDH_End = Sample.htm#End

Otherwise, it would be good to see your project (.hhp), header and alias files. Can you attach them to a reply?

Pete

[Richard Ferrell]

Does the CHM launch byitself without being called from your application?

[amyrn]

We just came upon a solution:
1. Double-click the Target to open the target properties tab.
2. Click the Advanced tab.
3. Under the Alias File section, click the Alias File menu and select (default).
The original item in this menu was defaulting to a RoboHelp alias, which couldn't be found. Now that this menu is reset to (default), MadCap .chms can now open correctly.

Thanks for your help!