Error Trapping

[jstevens]

I am having a challenge trapping error 53-File Not found.

Here is a sample of code I am using:

Code: Select all

'      On Error GoTo Skip 'in the event of a permissions error; remarked out to test the message box below 
      
             If Err.Number <> 0 Then
                MsgBox Err.Number
                    GoTo Skip
             End If

       Set objFile = objFSO.GetFile(.FoundFiles(x)) 'set the object to get it's properties; HERE is where it errors out.

Once the code errors out, I am able to step through the code by pushing back the start point to "If Err.Number <> 0 Then" and things work just fine.

Any suggestions would be appreciated.

Thanks,
John

[HansV]

You have to use some kind of On Error statement, otherwise the code will pause. For example:

Code: Select all

On Error Resume Next
Set objFile = objFSO.GetFile(.FoundFiles(x))
If Err.Number <> 0 Then
  MsgBox Err.Number
  GoTo Skip
End If
On Error GoTo Skip

Note that the check for Err.Number is after the instruction that could cause the error.

[GeoffW]

An alternative to error trapping is to use the dir() command to determine if the file exists, before attempting to open it.

[Don Wells]

An alternative to error trapping is to use the dir() command to determine if the file exists, before attempting to open it.

I don't think that will help in the instance where the file of interest is in use.