Hey Everyone, I am using WSS 3.0 and am aware of a workaround for allowing file:// to be used in conjunction with the Link to Document content type such that UNC paths can be used. A couple of questions I have, however, regarding this functionality are: 1. Is anyone aware of a workaround that does not require server interaction? 2. Has this issue been resolved in MOSS 2007 or are people still having to perform some kind of workaround within those platforms well? I appreciate any input on this matter. Thanks, John

Not require server interaction? The fact that the link lives on a SharePoint site, by its very nature, requires server interaction. As far as I know, the file:/// notation is only way to link to drive/file paths. I trust that answers your question... Thanks C http://www.cjvandyk.com/blog

I apologize for the confusion, what I mean by not requiring server interaction is that I don't have access to the server to modify the necessary WSS 3.0 files to allow for the file:/// notation to be used. Currently, it only allows http:// or https://. My questions then are these: 1. Is there any other ingenious way to get the Link to Document content type to allow you reference UNC paths or is modifying the JavaScript check in the server file the only method? 2. Has this oversight been fixed in MOSS 2007 (which we will be upgrading to) such that I could live with this limitation now knowing it will not be a problem (i.e. the file:/// is not blocked by the JavaScript) in the near future? I appreciate your time in responding.

We were able to get this resolved by adding an item and then going abck and editing it with the correct path. While it checked for http:// or https:// during the add process, it does not seem to do so when editing. This is a simple workaround that resolved the issue.