Comments

Does that error happen immediately when you select the File->Open All File in Directory Tree menu command or after selecting a folder and entering a filter? I just tried and it worked ok for me, so it must be something specific to your usage. If you try to open an individual file and navigate to the same folder does that also fail?

I have thousands *.shp and *.gpx in theses folders. When i chose less folders, data's displayed very well (i write *.gpx or *.shp).
But when i chose tree of several's folders i receive the bellow messages. I you have teamviewer software, i can show you the problem.
Sincerely,
HTUSER

When i shorten/correct the pathname, it work and continue the process. But, after other errors occurs and it can't open severals files as showed in the attached screen.
Does the problem is the length of the pathname?

Thank you for all. The first problem have been completely solved. That's work very fine.
But, there's a second problem. The software was unable to open some files. Nevertheless, theses files are opened once. Please can you ad a debugger at this level for the diagnostic of this trouble?

Looking deeper it appears that a lot of Windows functions are going to fail when the path gets longer than the old ANSI maximum path length of 260 characters. I can work around some of them using new API functions, but a lot of other calls are buried in 3rd party libraries. I actually couldn't even get Windows Explorer to let me create a filename and path combination that exceeded that limit, it actually blocked me from typing new characters or copying files into a folder whose name was too long.

Is there any way to limit the path length to get under that 260 character limit so it can work with everything?