Prevent Hyperlink warning

[thelemeuk]

Some systems with Excel 2003 always give a warning even when following
hyperlinks to local files. This has made an application in use by
researchers and clinicians unusable since it involves following frequent
hyperlinks to local sound (.wav) files.

I have looked at 2 discussions on this and understand from them that as yet
there is no resolution which works - would the download files developed for
Powerpoint work? and does Microsoft intend to address this issue in future
updates?

 

[Beth Melton]

Are you saying this resolution doesn't work for you?

http://support.microsoft.com/?kbid=829072

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

 

[thelemeuk]

I have one XPSP-2/Excel 2003 SP1 system to hand which does NOT manifest the
problem, but I have updated the registry as described on this system: I have
tried setting the security value to 0 and to 1 but 1 does not turn the
warning back on.

I also tried putting a security entry in the Excel component but that had no
effect either.

I have not yet had the opportunity to try it on another system which is
currently having this problem (Spanish Windows XP).

Thank you for looking at this

 

[thelemeuk]

FURTHER INFORMATION
Test in Excel 2003
1 Save any sound file (xyz.wav) on the C: drive in the root directory –
C:\xyz.wav
2 Start Excel
3 Type the following in any cell:
=hyperlink(“C:\xyz.wavâ€)
4 Click on the cell and observe whether a warning appears – if it doesn’t,
END TEST - there is no problem
If it does give the warning:
5 Save the workbook anywhere on the hard drive
6 Click on the cell again and observe whether a warning appears.
END TEST - this is what happened on my XPSP2 Excel 2003 SP1 machine

 

[thelemeuk]

I have now successfully implemented kb 829072 on a machine with Office 2003
standard edition. Thankyou. Do you know if the issue is addressed by Office
2003 SP1 and later? or is it possible that Microsoft may produce a utility
that will fix the registry safely without the need for end users to use
Regedit?