Instead of amending the URL, why not have a different redirect page for each product and control the page that is included by applying a build tag to the topic?
Just thinking out loud here... Rick
Helpful and Handy Links
Rick's solution is simple and elegant. I couldn't resist pointing out the hard way anyway.
Thanks for the feedback - here is more informtion on the challenges of this implementation:
I can only distribute one CHM file to cover all 5 web-based products that can be accessed through the Excel plug-in.
Regardless of which of our 5 products is used to install the plug-in on the client's local hard drive, the same installer is used.
That one CHM file is installed locally on the client's hard drive.
(The out of the box CHM file for the plug-in only has general plug-in help content the locl install causes problems for updating the content).
We needed to be able to easily update the help without inconveniencing the clients.
So, I am not creating 5 different CHM files for each installer, since there is only one installer regardless of how many of the 5 products they have.
The plug-in has a server setting and web service setting for each product and the client must choose which they are accessing when they fire up the plug-in.
They may be accessing the plug-in for any of our 5 web-based products they have subscriptions for.
Which means, the one CHM file must be able to:
(1) determine the product they are accessing
(2) direct to one of the 5 servers with the online help.
Each of the 5 online helps are deployed on separate servers with different URL links (and the helps have all different URL links as well).
These online webhelp outputs have some identical content but also some customized content for the specific product they are actually accessing.
My original approach was pretty much the same as William's above. Have a variable in the CHM help, determine the server they are accessing from the plug-in and insert the customized portion of the URL to access the appropriate webhelp.
Keep the ideas/suggestions coming.
I also have a development person looking into how to update a variable on the CHM side to populate the URL.
Michael F Weart
Another path I am researching, Map IDs.
Create a Microsoft HTML help project with 5 topics - one topic for each of the MicroStrategy data applications.
Each topic is assigned a map ID - from 1 through 5.
Each topic redirects the client to the application specific help (and the Excel Plug-In help is merged into it).
On the call to the CHM file from the Excel add-in, include the MapID based on the MSTR application it is linked to.
Example for call to hh.exe (example uses Map ID 2):
hh.exe -mapid 2 "C:\Program Files (x86)\MicroStrategy\Office\moimain.chm
The only problem here is if the development team cannot customize the call to the CHM help file.
Keep the suggestions coming as I may run into roadblocks on the options I am trying now.
Thanks to all --