Hi, UR, and welcome,
I believe that two things need to happen in order for the
context help calls that previously worked with a WinHelp project to
work with an HTML Help project.
1) Your developers must change their WinHelp API calls to
HTML Help API calls. This should be a fairly straightforward job
for them, as Microsoft modelled the HTML Help API on the WinHelp
API in order to simplify the process of updating existing
applications from WinHelp to HTML Help. For example, a typical
WinHelp API command looks like this:
WinHelp(HWnd, "helpfile.hlp", HELP_CONTEXT, 1001)
The HTML Help API equivalent is almost the same:
HtmlHelp(HWnd, "helpfile.chm", HH_HELP_CONTEXT, 1001)
For information for developers on how to call an HTML Help
file from an application, see these pages:
http://www.mshelpwiki.com/wiki/tiki-index.php?page=HTMLHelpArticles
http://msdn.microsoft.com/en-us/library/ms524256(VS.85).aspx
2) In the new HTML Help project, you must ensure that the map
numbers that the application passes to the help file are assigned
to the appropriate topics. This is described in RoboHelp's online
help in the topic called "Assign map IDs to topics", available
online at:
http://help.adobe.com/en_US/RoboHelp/RHTML/7.0/Context-sensitive/Map_IDs_and_map_files/Assigning_map...
It shouldn't normally be necessary to change the existing map
numbers and topic IDs just because you're moving from WinHelp to
HTML Help.
As with the old WinHelp project, the only file that you
should need to give the developers is the .chm file -— not
the map file as well. The only instance where this wouldn't be the
case is when you rather than the developers are responsible for
creating the map file, but that doesn't seem to true in your
environment.
Pete