Pdf filename length

Also, what version of Word are you using? Currently I am converting using the PDFmaker, then using the edit function on the Link Tool to fix up those links that do not work. I tried your link with Acrobat 9, Word SP3.

Once I changed it to C drive it started working. So do ensure that the destination that you are selecting is accessible from the machine where you care creating the PDF. Are your links created in similar fashion in Word? Unfortunately I can't get the files in your links to open.

We have a long weekend coming up so I will try to work out what the pattern is regarding filename size next week with our IT person. The links are all consistent, work well in the Word document and work well in the pdf document but won't if the filename is not too long end up with a document containing some links working and others not.

Thanks for your thoughts. Update to issue: after some more investigation, the problem still appears to be location based.

If the source document is in the first instance 2 directory levels and is output to the second, the links function. If the converse is carried out, they do not. The current workaround is to create the pdf in a higher level directory to retain the links, then to edit the footer in the resulting pdf which is then moved to the desired final location. You can do the next steps without reading the article, though.

The directory named This is inside the Documents directory. We want to copy the directory This and its contents into ThatNewFolder. Copying leaves the originals where they are and makes all new ones in the destination. Moving does not leave the original in place. The cmdlet will put This inside of ThatNewFolder.

It will also move everything that is inside of the This directory. Move-Item can be used to move files or directories, and it works regardless of file path or filename length. Then use the dir command to list the directories in ThatNewFolder. If we want to delete the This directory, and everything in it, we use the Remove-Item cmdlet. The Remove-Item cmdlet has some built-in safety that makes it difficult to delete a directory with things inside of it. Be warned! Recovering anything deleted this way would be extremely difficult.

No sense using PowerShell to do the work every day. There are two ways we can do this. We have encountered errors in the past if file names contained an apostrophes. The apostrophes still cause errors.

No special characters including brackets can be part of the filename. I believe something has truncated the filename and copied one file over the next until there was only one file remaining.

Submit ». Ghost Chili. Thanks to all for your thoughts. All 3 users, call them b,c,d are accessing a shared drive on user a's computer. Users b and c can open and email the long name files from that location, user d can't.

DylanB wrote: If there's a drive mapping involved, are users b, c, and d mapped to the same location? Dylan, Users b,c, and d are indeed mapped to the same shared folder on user a's machine. Kelly, Thanks for that suggestion, I will give it a try and report back.