Microsoft Office Forums

Go Back   Microsoft Office Forums > >

Reply
 
Thread Tools Display Modes
  #1  
Old 09-09-2025, 06:28 AM
chrisjj chrisjj is offline Word 2003 filepath characters safe for hyperlinks. Windows 7 64bit Word 2003 filepath characters safe for hyperlinks. Office 97-2003
Competent Performer
Word 2003 filepath characters safe for hyperlinks.
 
Join Date: Aug 2025
Posts: 120
chrisjj is on a distinguished road
Default Word 2003 filepath characters safe for hyperlinks.

Anyone know for sure the set of filepath characters safe for hyperlinks? I'm seeking workaround for the failure of [, { and # (https://www.msofficeforums.com/word/...03-2007-a.html).



Or... a scientific way to find out? Given I've found at least two modes of fail, I would be reluctant to rely on the results of trial and error.

Fun fact: ¦ is safe though | is disallowed. My UK keyboard has these two transposed, for some reason.
Reply With Quote
  #2  
Old 09-09-2025, 09:58 AM
Charles Kenyon Charles Kenyon is offline Word 2003 filepath characters safe for hyperlinks. Windows 11 Word 2003 filepath characters safe for hyperlinks. Office 2021
Moderator
 
Join Date: Mar 2012
Location: Sun Prairie, Wisconsin
Posts: 9,536
Charles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant future
Default

From: Naming Files, Paths, and Namespaces - Win32 apps | Microsoft Learn
Quote:
The following fundamental rules enable applications to create and process valid names for files and directories, regardless of the file system:
  • Use a period to separate the base file name from the extension in the name of a directory or file.
  • Use a backslash (\) to separate the components of a path. The backslash divides the file name from the path to it, and one directory name from another directory name in a path. You cannot use a backslash in the name for the actual file or directory because it is a reserved character that separates the names into components.
  • Use a backslash as required as part of volume names, for example, the "C:" in "C:\path\file" or the "\\server\share" in "\\server\share\path\file" for Universal Naming Convention (UNC) names. For more information about UNC names, see the Maximum Path Length Limitation section.
  • Do not assume case sensitivity. For example, consider the names OSCAR, Oscar, and oscar to be the same, even though some file systems (such as a POSIX-compliant file system) may consider them as different. Note that NTFS supports POSIX semantics for case sensitivity but this is not the default behavior. For more information, see CreateFile.
  • Volume designators (drive letters) are similarly case-insensitive. For example, "D:" and "d:" refer to the same volume.
  • Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:
    • The following reserved characters:
      • < (less than)
      • > (greater than)
      • : (colon)
      • " (double quote)
      • / (forward slash)
      • \ (backslash)
      • | (vertical bar or pipe)
      • ? (question mark)
      • * (asterisk)
    • Integer value zero, sometimes referred to as the ASCII NUL character.
    • Characters whose integer representations are in the range from 1 through 31, except for alternate data streams where these characters are allowed. For more information about file streams, see File Streams.
    • Any other character that the target file system does not allow.
  • Use a period as a directory component in a path to represent the current directory, for example ".\temp.txt". For more information, see Paths.
  • Use two consecutive periods (..) as a directory component in a path to represent the parent of the current directory, for example "..\temp.txt". For more information, see Paths.
  • Do not use the following reserved names for the name of a file:
    CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, COM¹, COM², COM³, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, LPT¹, LPT², and LPT³. Also avoid these names followed immediately by an extension; for example, NUL.txt and NUL.tar.gz are both equivalent to NUL. For more information, see Namespaces.
Reply With Quote
  #3  
Old 09-09-2025, 11:04 AM
chrisjj chrisjj is offline Word 2003 filepath characters safe for hyperlinks. Windows 7 64bit Word 2003 filepath characters safe for hyperlinks. Office 97-2003
Competent Performer
Word 2003 filepath characters safe for hyperlinks.
 
Join Date: Aug 2025
Posts: 120
chrisjj is on a distinguished road
Default

Thanks, but that's for filepath characters in general. For filepath characters in Word 2003 hyperlinks.
Reply With Quote
  #4  
Old 09-09-2025, 03:13 PM
Charles Kenyon Charles Kenyon is offline Word 2003 filepath characters safe for hyperlinks. Windows 11 Word 2003 filepath characters safe for hyperlinks. Office 2021
Moderator
 
Join Date: Mar 2012
Location: Sun Prairie, Wisconsin
Posts: 9,536
Charles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant future
Default

Here is the page on the Hyperlink field:
Hyperlink field
The # character is used to indicate bookmarks.
The " double quote character is used within fields.
I believe you've already looked at Paul's Word Fields and Relative Paths to External Files.


There is nothing wrong with you using trial and error. Then you can write the definitive answer.
Reply With Quote
  #5  
Old 09-10-2025, 06:45 AM
chrisjj chrisjj is offline Word 2003 filepath characters safe for hyperlinks. Windows 7 64bit Word 2003 filepath characters safe for hyperlinks. Office 97-2003
Competent Performer
Word 2003 filepath characters safe for hyperlinks.
 
Join Date: Aug 2025
Posts: 120
chrisjj is on a distinguished road
Default

Quote:
Originally Posted by Charles Kenyon View Post
Here is the page on the Hyperlink field:
Hyperlink field
The # character is used to indicate bookmarks.
There's no mention of that use on the page. And anyway, that use does not apply to the filepath.

Quote:
Originally Posted by Charles Kenyon View Post
I believe you've already looked at Paul's Word Fields and Relative Paths to External Files.
I have, but it doesn't relate to this issue, which is nothing specific to relative paths.

Quote:
Originally Posted by Charles Kenyon View Post
There is nothing wrong with you using trial and error. Then you can write the definitive answer.
Let's see if that's already been done.

Thanks.
Reply With Quote
Reply



Similar Threads
Thread Thread Starter Forum Replies Last Post
Copy footnotes into text - with hyperlinks and framing characters FLAYYMz Word VBA 2 11-25-2019 06:27 PM
Word 2003 filepath characters safe for hyperlinks. Word 2003 is getting problems - funny characters on the screen that do not print skkuchipudi Word 4 10-28-2015 09:18 AM
Word 2003 filepath characters safe for hyperlinks. Is it safe to reinstall Office 2003 from scratch now that support has ended ? Clairvaux Office 5 08-09-2014 08:51 PM
Word 2003 filepath characters safe for hyperlinks. need to email hyperlink (filepath) from word doc jackj22 Word VBA 7 05-29-2012 04:06 PM
Word 2003 filepath characters safe for hyperlinks. Outlook 2003 Receive Error unless in safe mode ranman1 Outlook 2 12-20-2010 07:37 PM

Other Forums: Access Forums

All times are GMT -7. The time now is 11:07 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
Search Engine Optimisation provided by DragonByte SEO (Lite) - vBulletin Mods & Addons Copyright © 2025 DragonByte Technologies Ltd.
MSOfficeForums.com is not affiliated with Microsoft