Hi, Steve,
That does the trick all right. Thanks for finding that out. So my
questions now have to do with what's the best thing to do for our users.
I'm assuming that the warning generation is intentional--that you guys
wanted to issue that warning--and it's not appropriate for our install
program simply to turn off (IT staffs might get pretty upset with us if we
did that) by default. Given that there's a registry key that controls
whether the warning is issued or not, can I assume that MS intended to
provide a facility from the UI to toggle this on or off (e.g. a check box)?
Will a service pack or something like that add the ability for the user to
control this functionality?
Otherwise, we can cook up our own solution which involves prompting the user
to have us turn off the warning for them, if they want when our custom URL
link gets inserted.
Thanks,
Mark
"Steve Culhane [MS]" wrote in message
...
Mark,
In researching this item, I found that this was reported as a bug, and
that
there is a KB Article in the works that provides a workaround. To fall
back and use Office 9 or 10 behavior all you have to do is add an entry to
the registry.
The location for the entry is
HKEY_CURRENT_USER\Sortware\Microsoft\Office\11.0\C ommon
- From here add a new key called Security
- Under this key add a DWORD Value called DisableHyperlinkWarning
- Set the DisableHyperlinkWarning value to 1
Setting the DisableHyperlinkWarning value to 1 overrides Office11
hyperlink
warnings. If the value is set to 0 then the warnings are enabled again.
I tested it and it looks like this solves the problem.
Thank you.
Stephen Culhane
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
| X-Tomcat-ID: 345854875
| References:
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (Peter Huang [MSFT])
| Organization: Microsoft
| Date: Mon, 29 Sep 2003 09:55:56 GMT
| Subject: Following a custom protocol hyperlink causes a warning in
Excel (Office) 2003
| X-Tomcat-NG: microsoft.public.excel.programming
| Message-ID:
| Newsgroups: microsoft.public.excel.programming
| Lines: 58
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.excel.programming:419660
| NNTP-Posting-Host: TOMCATIMPORT2 10.201.218.182
|
| Hi Mark,
|
| I am researching the issue and will update you with new information
ASAP.
| Have a nice day.
|
| Regards,
| Peter Huang
| Microsoft Online Partner Support
| Get Secure! www.microsoft.com/security
| This posting is provided "as is" with no warranties and confers no
rights.
|
| --------------------
| From: "Mark Rubin"
| References:
| Subject: Following a custom protocol hyperlink causes a warning in
| Excel (Office) 2003
| Date: Fri, 26 Sep 2003 07:47:58 -0700
| Lines: 31
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID:
| Newsgroups: microsoft.public.excel.programming
| NNTP-Posting-Host: adsl-66-218-52-192.dslextreme.com 66.218.52.192
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.excel.programming:419145
| X-Tomcat-NG: microsoft.public.excel.programming
|
| I should have noted in the post (as I did in the subject) that the
warning
| only occurs with Excel 2003. Also, I just realized that the same is
true
| for the other Office apps I've played with--no warning before 2003, but
a
| warning with 2003.
|
| -- Mark
|
| "Mark Rubin" wrote in message
| ...
| If you insert a hyperlink with a custom protocol or even, say, the
file:
| protocol, Excel will generate a warning message:
| "Hyperlinks can be harmful to your computer and data. To protect
your
| computer, click only those hyperlinks from trusted sources. Do you
want
| to
| continue?"
| If you say you do want to continue, things proceed as expected.
|
| I've got a program that inserts hyperlinks using a custom URL
protocol
| into
| cells. In 97-XP, users can click on the hyperlink, and my custom URL
| protocol handler will get called and do what I like. Now users have
to
| go
| through an extra step of clicking through this warning. Although I
| understand MS's concerns here, does anyone know how a user can elect
to
| trust my protocol handler and avoid this message?
|
| Thanks,
| Mark
|
|
|
|
|
|
|