Runtime 1004 error on existing file

[Pobek]

I am getting this error when I point my macro to a file in a specific directory. Problem is THE FILE IS THERE!!! There are some actions that I have taken:

1. I made copies of the same file with varying length in names.

2. The file with the shorter names are found whilst sometimes the files with the longer names have part of the end cut of (i.e. a runtime error when a filename such as "September-DB" is being looked for under "Septembe" .... cutting off the "r-DB". HOW ON EARTH IS THIS THE CASE!????

3. Copied all the input files in their input folder to a shorter directory (a Path not so long) and for this shorter path, the macro finds all files (including the ones with longer names).

It seems that there is something that is making my code cut of the end of some of my file names particularly if they are sitting in a long and deep file-path ... could there be a limit to the length programmed somewhere? I doubt this as its not the 1st time I have developed models that look for long file names in deep and long file-paths ... HELP!!

I have a 2013 excel.

 

[Pobek]

OK, try changing the message box line to this now:

MsgBox Opfile

Then, when you get an error, check to make sure that you actually have a file by that exact name that currently exists in that exact file path.
I suspect that there may be an error in there somewhere.

Trust me I have, but I'll do it again just to make sure.

 

[Joe4]

Yes, be sure to check very carefully for things like spaces, I's that look like 1's, 0's that look like O's, etc.

Some other things I have seen trip people up before:
1. The path is different for different people (due to drive mappings, permissions, etc). Make sure that you can open it by browsing to the exact same path in Windows Explorer.
2. There is an issue with the file (already open, corrupt, bad extension so it cannot be opened). Can you browse to it and open it manually via Excel?

 

[Pobek]

Yes, be sure to check very carefully for things like spaces, I's that look like 1's, 0's that look like O's, etc.

Some other things I have seen trip people up before:
1. The path is different for different people (due to drive mappings, permissions, etc). Make sure that you can open it by browsing to the exact same path in Windows Explorer.
2. There is an issue with the file (already open, corrupt, bad extension so it cannot be opened). Can you browse to it and open it manually via Excel?

Hi, how are you.

I have and it opens. I guess there some spaces there but that hasnt stopped it in the past.

One thing I did notice though is that part of the file extension was copied over from a usb. Now while the whole extension being referred to sits on my local drive, I notice that some of the sub-folders (the part copied from the usb drive) have a blue man-torso like figure on them. When I link the macro to an extension that has all folders originating from the C ... there are no issues. I suspect this might have something to do with it...what u think?

 

[Pobek]

Not quite a torso as it is the figure of a man from the shoulders/chest up

 

[Joe4]

I notice that some of the sub-folders (the part copied from the usb drive) have a blue man-torso like figure on them.

I have no idea what that is...

 

[thisoldman]

I think the little blue man icon indicates the folder is shared.