Persistent error executing a Name function

[GraeagleBill]

Below is a screenshot of a persistent error raised when I attempt to rename a file. The error handler messaging includes an exact copy of what amounts to the program statement that raised the error.


I cannot see anything wrong. I cannot even guess what might cause the input file to be open, even if it was, I would expect an error indicating as such. The 3rd-party ffmpeg app just concluded converting a wav file to the mp3 file seen here as the input to the rename.



Thoughts?

WOW, now with a close-up view seen in the screenshot, I see the play duration includes NO NO colons in the expression.

[pbaldy]

Glad you sorted it Bill! I was going to suggest debug printing the path and seeing if it was valid. Bad eyesight, I couldn't tell those were colons rather than semi-colons.

[GraeagleBill]

Well, to give a better idea of how bad my eyesight has become, I started with a few Debug.Print approaches but still didn't see the colons. It was only with the enlarged screenshot. There is a reason for the "Old Geezer" avatar.

[Welshgasman]

Perhaps increase the font size on your computer, if that is the case.