A
Alex Stevens
Hi All,
I'm asking for opinion for the best way forward with storing the path of a
network shared document in a SQL Server table.
Essentially, I want to store in a part record the path to it's actual word
document on my client's network.
Currently, I am storing the mapped drive path when the user selects it using
the OpenFileDialog object in VB.net.
This is all very well if all the users have the same mapped drives - and
they may not.
So I think I should store the UNC path of the file - this is what I 'd like
peoples opinions on.
Should a user on one PC with a network share mapped as R: and another user
with the same share mapped as T: be able to access the file
\\ServerName\Directory\Filename.doc ?????
Are there any issues to consider? If the user doesn't have proveledges to
read the share, that doesn't matter - they just won't get access to it.
How can I get the UNC path of a file in vb.net.
I've tried the WNetGetConnection approach but that returns a empty string?
Thanks
Alex
I'm asking for opinion for the best way forward with storing the path of a
network shared document in a SQL Server table.
Essentially, I want to store in a part record the path to it's actual word
document on my client's network.
Currently, I am storing the mapped drive path when the user selects it using
the OpenFileDialog object in VB.net.
This is all very well if all the users have the same mapped drives - and
they may not.
So I think I should store the UNC path of the file - this is what I 'd like
peoples opinions on.
Should a user on one PC with a network share mapped as R: and another user
with the same share mapped as T: be able to access the file
\\ServerName\Directory\Filename.doc ?????
Are there any issues to consider? If the user doesn't have proveledges to
read the share, that doesn't matter - they just won't get access to it.
How can I get the UNC path of a file in vb.net.
I've tried the WNetGetConnection approach but that returns a empty string?
Thanks
Alex