File/Hyperlink Problems in a Networked Environment

Vessel Management System Professional

Back    Home

File/Hyperlink Problems in a Networked Environment


The paths (locations) of File/Hyperlink associations are computer specific.  So you might assign an object on your bridge computer and then find it's not usable on the engine room computer.


To solve this problem (in a networked environment where none of the computers are mobile) place all your object file/hyperlink associations on the computer that acts as the central repository of data (the data server).  Even if that server happens to be the computer you normally use (local), it's files can still be accessed and associated as a network link.  


When you associate a File/Hyperlink from the networked view of your local computer the association will look the same to all computers that use it.  This convention may be particularly critical if all original associations are made on a parent computer with the intention of making associations valid on all the children.   


So a local computer named JoeComputer with a  File/Hyperlink association that serves as the master repository of associations would have an address like: 



rather than



On the other hand, you might want to keep your File/Hyperlink associations on the local computer, such as might be the case with a laptop that needs to travel, or one that operates in the network, but needs to keep File/Hyperlink associations private.  In that case you would check Keep Local Hyperlinks in the Network Directory Assignment module before you guide VMS to the associated object.  This will cause all the File/Hyperlink associations to be kept on your local computer, but they still need to be assigned.


You may utilize this utility to use networked object file/hyperlink associations from the data server while working in a networked environment and local object file/hyperlink associations while working on a single computer.


In this scenario you could make all the associations on the network server computer as local hyperlinks, then copy all the associated files to the traveling computer and deposit the folders containing the files into exactly the same location (such as C:\Program Files\VMSPro\Images).  Now the local file/hyperlink associations first established on the server will work locally on all it's children.


One downside to the above method is that all objects will need to be synchronized occasionally between computers so that all will be referencing at the same version of the same objects.  To make this as easy as possible, place all the file objects that you want to associate in a folder that can be made common to all computers by copying or reconciling.