Quote:
Originally posted by Pat Phelan
I'm confused. UNC names and FQDN names aren't the same thing, and they aren't either sub or super sets of a common thing. Your question makes as much sense to me as "How do I turn a lemon into a brick?" because of the disconnect.
I must be missing something. Can you give me an example?
-PatP
|
Pat,
I have a facility that allows users to store links to documents (e.g. Word Excel, etc). To ensure that these links can be used by users with different logical drive mappings I store the UNC path of the document. We are now upsizing the application to an enterprise application running on multiple domains across a WAN. I have been requested to use FQDNs rather than UNCs to ensure that the document links are unambiguous.
I take your point that FQDNs and UNCs are the same thing, what I was trying to get was a FQDN based format for a file selected from the Office open file dialogue (I currently retrieve the UNC from the result of this). I see no easy way of doing what I want so I have implemented my own code that resolves the server part of the UNC into a FQDN format using centralised lookup tables. It introduces a bit of ongoing lookup table maintenance overhead, but I can’t see any easier way of doing it
Thanks for your help
Brian