Hyperlink

[KeisukeNozaki]

Is there a way to hyperlink a field from a related table in ArcGIS Desktop 10?
I cannot join the table because it is one to many relationship.
I prefer field based hyperlink, not dynamic hyperlink, because there are thousands of features.

[RichardFairhurst]

it works with paths relative to the mxd location..
but if in the Map Document Properties I've decided a different "Hyperlink base"... why it doesn't use it?

I think that only applies to a layer that defines a single field as a Hyperlink in the layer definition.  I do not think it applies to the general setting that enables anything resembling a hyperlink to fire up.  I do not believe that setting should apply to that condition, since all manner of hyperlinks are supposed to work though that setting, not just those from a single base.  I would not want it to be limited.

How would distribution transfer the linked information that would cause you these problems?  If the links aren't in relative path configuration, don't you risk a break in the link anyway if the other user does not duplicate your directory conventions locally or have access to your domain?  What UNC are you using in the base?

[DuccioNotari]

I'm working in a standardized model made by geodatabases in specific folders, so everyone that will get my work will have to use this folder's structure.. it may change the letter of the drive, or there may be some more folders before mine but the standard is fixed.. so I was hopin that it would work better for everybody if there was no dependancy from the place you put my folders.
this is the full path to my mxd
D:\lavoro\GIS\AereoportoS15\Progetti\ArcGis10\project.mxd
and this is the full path to the liked documents
D:\lavoro\GIS\AereoportoS15\Carta_delle_indagini\Documenti\example.pdf

If I understood well, in my field I should write
..\..\Carta_delle_indagini\Documenti\example.pdf
correct?
I was hoping there was a way to use shorter paths by specifying a common starting point that is "nearer" to the desired documents because some documents have got really long names ad are in sub-sub-folders of "Documenti".. so the hyperlink field has to be very big and it's not that easy to understand what are you opening just looking to the field.. I mean.. there's a difference between seeing "example.pdf" or "..\..\Carta_delle_indagini\Documenti\example.pdf" or longer!

[RichardFairhurst]

I make no effort to make the hyperlink field human readable or displayable.  I use other fields as my display field for the identify tool, so I don't care what the hyperlink is (I never use the hyperlink tool, just identify).  I would suggest that is how you should view that field. 

I do not use drive letters at all or relative paths.  I use the UNC //agency/agencydfs/ for my files which is a domain file server domain name that has been set up by my IT department.  It can point anywhere that my IT department wants (multiple servers are accessed with that same UNC prefix and are distinguished by whatever the next portion of the path is named).  Virtually everyone in my domain can see the information from the dfs (IT can restrict permissions if needed) and IT is free to move the pointer from server to server as they want without breaking my links as long as they preserve the directory structure below the pointer.  It is very convenient and I do not distribute the hyperlink material normally (for the few people outside my domain I just have them use the Field Calculator and a replace operation to alter the path, but most of them are getting access to the domain to avoid information latency and portable harddisk sharing).