J
JVW
I have an Excel add-in. I originally wrote it in VBA, then converted it to
Visual Basic. I have the same problem in both cases.
I have a ".chm" Help file which I call from my add-in using
"Application.Help(filename)" where "filename" is the full path and name of
the ".chm" file. It works fine in Vista and XP but not in Server 2003.
Apparently a security fix to Server 2003 blocks the command. I don't get an
error - it just doesn't load the Help file.
There are a lot of things written about this problem by Microsoft and others
but it seems like they all want me to alter the registry. My application is
written for commercial use so I can't ask all the companies to alter the
registry just for my application. Is there some work-around for this so I
don't have to alter the registry? Or is there another way to call the Help
file that gets around the restriction?
Visual Basic. I have the same problem in both cases.
I have a ".chm" Help file which I call from my add-in using
"Application.Help(filename)" where "filename" is the full path and name of
the ".chm" file. It works fine in Vista and XP but not in Server 2003.
Apparently a security fix to Server 2003 blocks the command. I don't get an
error - it just doesn't load the Help file.
There are a lot of things written about this problem by Microsoft and others
but it seems like they all want me to alter the registry. My application is
written for commercial use so I can't ask all the companies to alter the
registry just for my application. Is there some work-around for this so I
don't have to alter the registry? Or is there another way to call the Help
file that gets around the restriction?