The CHM file has to be located in the same directory as the database that is to use it as a help file. Place the following code in each form's on_open event, preferrably before doing anything else on the On_open event. Here is a quick work-around that will enable the users to see the complete help file regardless. The help file can be displayed will all content if the help file is on the local machine that is useing the application. The user will be able to see the TOC (Table of Contents) but does not allow the actual content to be displayed. Microsoft in its infinite wisedom does not allow help files (.CHM) that reside on a server share to be displayed. Because help files are viewing local content and script is allowed to execute in CHM files there's potential for malicious code hiding in CHM files and the above precautions are supposed to avoid any issues. It's annoying as all hell that this sort of obtrusive marking is necessary, but it's admittedly a necessary evil because of Microsoft's use of the insecure Internet Explorer engine that drives the CHM Html Engine's topic viewer. A fully installed Help File of an application works just fine because it is trusted by Windows. However, if the help file is installed as part of an installation the installation and all files associated with that installation including the help file are trusted. The above security warning pop up because Windows can't validate the source of the CHM file. How to avoid this ProblemĪs an application developer there's a simple solution around this problem: Always install your Help Files with an Installer. Since most help files don't contain script or only load script that runs pure JavaScript access web resources this works fine without issues. In recent versions of Windows Internet Explorer pops up various security dialogs or fires script errors when potentially malicious operations are accessed (like loading Active Controls), so it's relatively safe to run local content in the CHM viewer. Is unblocking insecure? Not unless you're running a really old Version of Windows (XP pre-SP1). You can also use a Powershell command to do this (on Windows 10): PS> unblock-file -Path '.\westwindwebtoolkit.chm'
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |