MS Word that is. I want the MS client browser to be able to launch word. I’ve got that figured out, but I have to change security to Custom – “Initialize and script ActiveX controls not marked as safe for scripting” (This is an inter office app used by maybe 5 people).
That would work, but I would like to get this set JUST for word. Looks like I can do it in the registry. Using regedit.
So, by looking at the not so helpful MS article, it looks like if the above CLSID’S are added under ‘Implemented Categories’ UNDER the primary CLSID, the object will be marked safe for scripting.
My problem is I can’t figure out what the CLSID is for word? I would think that I could GOOGLE it, but come up empty.
Yep, I know there are pitfalls; versions will have different CLSID’s. Maintenance therefore would be heavy (we are only talking about a few machines though). But now I’m curious if my idea has any viability at all. I don’t think it would be a big deal to just open up security on the browsers a little bit for 5 machines. But I’m looking for options to present to my boss.
{000209FF-0000-0000-C000-000000000046} is the version-independent CLSID for Word.
In general they can be found by searching for a key named “<Name>.Application” in the HKEY_CLASSES_ROOT section of the registry.
If you go to “HKEY_CLASSES_ROOT\Word.Application”, you’ll see a subkey “CLSID” which is what you’re looking for. You’ll also see keys for Word.Application.11 or .12 or .8 or .<WhateverVersion> for the specific CLSIDs for the various versions.
In Word’s case all the versions my box has ever seen use the same CLSID. It’s possible that Word 3.0 (e.g. from 1989) used a different version-specific CLSID, or that Word 14 (whenever it comes out) will have a different version-specific CLSID.
But as long as you use the lowest common denominator functionality of the current version-independent CLSID, your code should work fine when O14 gets installed without your knowledge. The whole point of version-independent CLSIDs is to make a promise for all time that code accessing that interface will get the same behavior in all future versions forever. And that is where a lot of code bloat comes from. Even if some function was implemented kinda quirky in, say, Word 95, it still has to have all those same quirks in Word 14.