Dir() Error 52: Bad file name or number

[ChipR]

I'm using

strFileName = "\\serverName\folderName\fileName.txt"
If Dir(strFileName) > "" Then
...

This worked fine for me, even when I disconnected from the network, but when a user ran it on an unconnected laptop the Dir line threw an Error 52: Bad file name or number. It seems like Dir should just return an empty string instead of an error in any case.

Anyone know why it would do that?

[ADezii]

@ChipR
This appears to be the Default Behavior for Network Paths, just set a
Trap for Error Number 52 as in

On Error GoTo Err_Test_Click
strFileName = "\\serverName\folderName\fileName.txt"
 
If Len(Dir(strFileName)) > 0 Then
  'File/Path OK, code execution begins here
Else
  'don't really need this, an Error will be generated
End If
 
Exit_Test_Click:
  Exit Sub
 
Err_Test_Click:
  If Err.Number = 52 Then   'Bad File Name or Number
    MsgBox "File or Network Path not found!"
  Else
    MsgBox Err.Description, vbExclamation, "Error in Test_Click()"
  End If
    Resume Exit_Test_Click

[ChipR]

Thanks ADezii, I did that to handle the error, but I was surprised by what seems to me to be an undocumented error result. It worries me about what other errors could magically pop up that I can't possibly forsee, but I guess I'll just have to fix them quick when they happen.

[ADezii]

@ChipR
Do not despair, ChipR, for here is a clean and efficient alternative:

'Must set a Reference to the Microsoft Scripting Runtime
Dim fso As FileSystemObject
Dim fil As File
 
Set fso = New Scripting.FileSystemObject
 
If fso.FileExists("\\serverName\folderName\fileName.txt") Then
  'code execution here
Else
  MsgBox "File and/or Path cannot be found", vbCritical, "File Not Found"
End If