If you use context-sensitive help, keep in mind that HTML Help uses a different API from WinHelp. The developer will need to make changes to the code to implement HTML Help API calls.

Theoretically, the developers should be able to figure out how to make the changes from the development tool documentation, their subscription to MSDN, and all those programming courses for which your company spent all that money. In reality, the developers will come to you to ask you how to make the switch (which is okay because you should know this information anyway). Here is some basic information that will point you and the developers in the right direction:

• If you are using Visual Basic 6.0 or later, the change can be as simple as specifying an HTML Help .CHM file instead of a WinHelp .HLP file. This will change any help calls you have Visual Basic make for you automatically to HTML Help, although you will probably need to do some fine tuning. Developers will need to revise any API calls they coded manually.

• Refer the developers to the HTML Help section of the Microsoft web site. (The URL is current as of 26 February, 2000, but URLs are subject to change.)

• The HTML Help API has calls for context-sensitive help that are similar to what the developers may already be using for WinHelp, such as HH_HELP_CONTEXT in place of HELP_CONTEXT to call help by help ID.

• Some help authoring tools offer custom What's This? help that supports multiple fonts, graphics, and jump links. The developer needs to incorporate the custom OCX files into the code, and you need to ship those files with the product. See the help authoring tool documentation for instructions.