Hi again
Indeed if you are using an application to install your
company's application, it will need to be aware of your new files.
So you need to get your CHM file(s) into the hands of the person
that maintains that application.
However, I'm guessing that once you cross this hurdle, you
will likely STILL have an issue. Here's why.
Your developer's statement of:
Our developer thought that simply replacing the Help files would
suffice. is worrisome, to say the least. This is because if you
are switching from WinHelp (.HLP and .CNT files) to Compiled HTML
Help (.CHM files) the calls issued from the application will most
likely change.
Let's step away from the help arena for a bit and step into a
different realm that may help you to better visualize/understand
things. Consider that your application is like an electric stove.
When the help is opened, the stove is expecting to use electricity.
The problem here is one of connections. Essentially you have
replaced the old help (electricity) with a new type of hep (natural
gas). As a result, you must now run a gas line and change the stove
(your application) so that it understands how to use natural gas.
In other words, it's never as simple as dropping a .CHM in
where a .HLP existed and expecting it to work. The application
needs to understand it is looking now for a .CHM instead. And your
developer should know that.
Cheers and good luck... Rick