Link to home
Start Free TrialLog in
Avatar of askolits
askolits

asked on

VB6 FileSystemObject works with UNC but not with mapped drives on Win7 PC

This is happening on a customer site. I'm trying to use FileSystemObject on a Win7 PC to see if a file exists. If I use the mapped drive, a good filename returns false, UNC returns true.  I also tried an old method:
 Dir(CStr(Filename)) <> ""
Same results.

I tested this at home and I don't have a problem. Yet, I have a workgroup based network.
The customer's Win7 PC is on a domain. I do have administrative rights on that domain but mapped drive still fails. Note: UAC is turned off.

They never had a Vista PC. Just starting to deploy Win7. Previous version (Win XP) does not have the problem.

Looks like some type of Win7 rights issue, but not sure.




Function lbf_FileExist(strFileName As String) As Boolean
Dim ofso
Set ofso = CreateObject("Scripting.FileSystemObject")
        ' Check for file and return appropriate result
        If ofso.FileExists(strFileName) Then
               lbf_FileExist = True
        Else
               lbf_FileExist = False
        End If

End function

Open in new window

Avatar of Ivano Viola
Ivano Viola
Flag of United States of America image

IF the script runs as administrator, then Administrator (the user) does not see the mapped drives as it runs as a different user. The mapped drives are only for currently logged in user. UNC paths work just find as long as the path exists.
How are you mapping the drive? Windows 7 has some strange behaviors when dealing with "normal" mapped drives sometimes. Try and map it from the server's user's policies (bat file) to see if the error continues.
Avatar of askolits
askolits

ASKER

ivanoviola: "The mapped drives are only for currently logged in user. UNC paths work just find as long as the path exists. " 
 Well it's mapped for both types of users and the issue happens both times.
 
Caracena:"Try and map it from the server's user's policies (bat file) to see if the error continues. "

I'll ask the network admin to look at this posibility.
"Well it's mapped for both types of users and the issue happens both times....."
I'm not sure what you mean when you say that.

My point was that if the script runs "As Administrator" while logged in as Joe Blow, the script will not see Joe Blow's mapped drives. That's why it fails.
Hmm... Maybe.
I logged in as myself and I am an administrator and it failed. But I didnlt actualy use the "Administrator" username. I'll have to try it and see.
 
I've run into similar problems when programs that need to run "As Administrator", and use a mapped drive, fails to run correctly. When I change the drive mapping in the config file to a UNC path, all is good.

I think the same problem is happening to your script.
ASKER CERTIFIED SOLUTION
Avatar of askolits
askolits

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial