UNC path and absolute path

Discussion in 'SolidWorks' started by GK, Aug 30, 2006.

  1. GK

    GK Guest

    We have some assemblies with some parts referenced using the UNC path
    (//server/foldername/filename) and some with absolute path
    (J:/foldername/filename), I dont know why . Recently i remapped J: as
    G: and had trouble opening the assembly.
    Does any one know why some files have UNC path and other absolute.?
    Any help is appreciated.
    Thanks
    GK
     
    GK, Aug 30, 2006
    #1
  2. GK

    John H Guest

    It depends on how the user browsed to the component when it was added to the
    assembly.
    Interestingly, if you add a component via its UNC path and then add a second
    copy using its mapped drive letter, they both appear as using the UNC path.

    What's the general opinion of this forum of UNC vs mapped drives?
    I'm sure I read something a while back saying that UNC was the way to go,
    but that seems the wrong approach to me.
    The obvious beauty of the mapped drive is that you can change the physical
    location of the data without breaking any links.

    Regards,
    John H
     
    John H, Aug 30, 2006
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.