Thank you for your post. I had entered dummy files.
I noticed that if the file paths are very long (multi line after I paste), the whole macro from display of search box to execution goes haywire which basically makes it useless
I am going bananas trying to troubleshoot this
Have you got an actual failing path you can post as an example? This seems particular to your setup rather than a general KM issue, so we'll need to be as close to what you're doing as we can be.
I would guess that you are entering carriage returns when you should not be.
Post the whole macro as it was when it went wrong as you describe in the above quote. That way we will be able to see exactly what is going on, rather than having to rely on just your description.
Again -- post an example of a path which breaks it. We might be able to put our heads together an come up with a fix -- my first thought is that if all your files are in the same subsection of your directory tree you might be able to prune the "constant" prefix before displaying it, then add the prefix back in before opening it.
I sometimes have to deal with similar, eg file paths with potentially confidential info. The trick is to copy the path, replace all the A-Za-z0-9 characters with the same number of a (or any other single character) but keeping any potentially "special" characters in there in case they are the problem.
Create that new path and file and test to see if the problem still exists -- if so you can happily send off that new path in your problem report and Support can test for path length, special characters, etc, without you divulging potentially sensitive information.
They're obviously not too long for the OS, just for one (or more) parts of the macro. I'm suggesting that there may be ways to work round that, but without an example "bad" path to work with it'll be difficult to reproduce the problem.