I have an application that reads a CSV file into an Execel table.
Here is my code. It works on my machine. With a correct file path and file name, I skip over the msgbox and compute on. With a deliberately bad file name, the code jumps into the if statement, I get the message box and the subroutine exits. Perfect execution. The offending line is highlighted in red.
The problem is that two of my co-workers are not getting this code to work. Instead of NOT finding the file (they may or may not have access to the directory) they get the error message Run-time error '52' Bad file name or number. Now, could this be that I can't even test if a file name exists if they don't have access to the server? If so, how does one test that one can't reach a file on the server?
Yes, I can attach the files, but I'll have to do a lot of work to the data to desensitize it.
![]()
Please Login or Register to view this content.
Bookmarks