This content has been marked as final. Show 2 replies
Here's my humble opinion - just use the 17 different topics and create the 17 map ids.
Noone wants to scroll through a topic that is so long they lose their place. Even if they come in at the right place, it doesn't take much to become disoriented in a lengthy topic.
It is no big deal to create and maintain map IDs. I have over 1000 in mine, and trust me - they take up a negligible portion of my day, if at all. Once they are set up, there is no further maintenance needed unless you add new forms or change the name of existing forms.
Having said that, no doubt there is a way to set up bookmarks and link them to map IDs in the manner you want, but someone else will have to fill you in.
I urge you to rethink your strategy. What you want reminds me of the old-fashioned Help files that were basically just Word documents pasted into single topics that went on for miles.
Good luck, with whatever method you end up using!
Each context integer that the application passes to the help system can be mapped to one topic (or bookmark within a topic) only. So, you need 17 different context integers — one for each Help button — to go to 17 different locations within the help system.
You have the choice of keeping the single big topic, with bookmarks inserted at the appropriate places, or of splitting it into 17 topics. In both cases, you require 17 different integers that you can map to the bookmarks or topics.