objfso.Drives(name).ShareName Not Working on Some Computers

[JonMulder]

I have a function that uses File System Object to get the actual network name of a drive. Today, a remote user had it crash when I tried to return the Sharename.

Function GetUNC(LocalPath As String) As String
MsgBox ("GetUNC Function")
Dim objFso As FileSystemObject
Set objFso = New FileSystemObject
Dim strDrive As String
Dim strShare As String
strDrive = objFso.GetDriveName(LocalPath)
strShare = objFso.Drives(strDrive).ShareName
GetUNC = Replace(LocalPath, strDrive, strShare)
Set objFso = Nothing
End Function

Specifically, it fails on "strShare = objfso.Drives(strDrive).ShareName" line.



The incoming LocalPath variable is "P:\GroundwaterDatabases\GWIDS\ImageLocationMap\Gl ennCounty_Book3\21N04W12A002M_LocationMap.jpg"

I want to change LocalPath to \\nasnro\Projects (i.e., replacing the LocalPath (P) with the network path (\\nasnro\projects).

Any idea why it doesn't work? It's been doing fine for months on other computers.

Thanks for any help you can provide!

Jonathan Mulder
Engineering Geologist
California Department of Water Resources

[Dal Jeanis]

Total speculation, but I notice that the original "Path" has the name of a jpg file in it. Does that file even *have* a Sharename property?

[JonMulder]

Thanks for the reply, but I don't think that's the issue. I just rant it on my computer and it DOES return a value for strShare. BTW, the extra space("Gl enn") is a typo. The actual code contains no space in the string.

[Dal Jeanis]

k. Well, perhaps you can get the actual error number and message language the next time.

It can't be a one-shot LAN drop because you would have tested the issue multiple times before posting here.

I'd next be checking all the operating system details, references and addins of the offending system for differences from the standard, checking 32 bit vs 64 bit settings and so on. However, the Sharename property should be a property of the drive itself, so it would take a pretty big hickey in the local operating system to obscure that.

I'd also cobble together a paranoid version of the code - display the strDrive, check DriveExists and IsReady, might even code it as Drives.Item(strDrive).ShareName, although that should have no effect. If any of those failed, you'd have more clues.

There is this little note in the Drive information section of this page http://msdn.microsoft.com/en-us/libr...(v=vs.71).aspx :

If more than one person can open the project on the network share, you can use an MS-DOS environment variable to give each person a customized mapping for the share.

Probably not relevant, but it just clunked when I read it.

[JonMulder]

Dal,

Thanks for your suggestions on this. I've trimmed down the database to just the few lines of code and it still doesn't work. My remote user get a run-time error "Invalid procedure call or argument".

What's odd is that the line preceeding the offensice line ("objFso.GetDriveName(LocalPath)) DOES work, so at least the Microsoft Scripting Runtime reference library is working.

I'll keep mucking with it. Again, thanks for the feedback.
"

[Dal Jeanis]

So, what did DriveExists and Isready return when placed between those two lines?

[JonMulder]

Haven't tried that yet. I'll get back to you.