Linked in general theory to this (
http://forum.lazarus.freepascal.org/index.php?topic=26488.0) but different as it relates to finding and reading files...
The Windows MAX_PATH limit of 260 characters for folders and filenames is causing a problem with a program I have made that searches for files. It works fine for all files except the ones that are in folders that are greater than 260 chars.
Though it is true that there aren't many software tools that can create folders and files longer than that depth, there are some. However, if the user then eeds to use "normal" windows tools to access those files, they either don't detect them or they generate errors.
In my case, my colleagues are using my program to copy data across our network and benefiting from the hash CRC checks it does. However, lets say there are 10K files in FolderA, we're finding it might only be copying 9,990 to the destination folder. It turns out the 10 missing files are files that, in Folder A, are in folders longer than 260 characters.
My program uses the TFileSearcher type which in turns uses FindFirst and FindNext compiled using Lazarus 1.4.0 and FPC 2.6.4 - my stable programming environment.
I gather FPC v3 uses unicode aware versions of most of the functions like FindFirstW etc that can detect files in paths of lengths of 32K characters, but I don't especially want to code a program using yet another version of the language because I'll end up getting muddled up and compiling some programs with one version and others with another version etc.
So my question is how can I ensure files are FOUND if they live in folders whose path is greater than 260 chars using the FPC 2.6.4 instances of TFileSearcher?
Recent
