>>>>>Since the Win platform is case-insensitive AFA filenames, I don't see what the issue is IAC, but people will complsin about whatever solution they're provided...
>>>>
>>>>One problem is cross-platform support - I ran into the problem in transferring files through a system that had case sensitive filenames, no problem getting them there, but getting them back was a problem as the names no longer matched.
>>>
>>>Use the wrong tool, get the wrong results...
>>
>>Yeah, bad mistake using VfP - need to use something not produced by Microsoft to get the right results - I should have learned after all these years of using MS stuff that you just shouldn't expect their tools to be suitable for their own operating system.
>
>Ni, it -is- suited to -their- operating system, and to operating environments that publish a compatible filesystem, where case-sensitive filenames are not an issue. You have multiple tools, including native tools in VFP, to retrieve case-sensitive filenames (the FSO, Win32API calls and any other of a number of mechanisms that -advertise- that they maintain case-sensitivity.) YMMV, but it helps to read the docs to see what the expected behavior is before making an irrational assumption...

My personal observation would be I wouldn't want to see this changed. In my mind, it's an issue of style versus substance. I'll stick with the substance. If I issue ADIR() and I want to sort the result set, I don't want to go futzing around with the collation sequence in order to have it produce the correct, or at least anticipated, results. If I want want the original case, or something else, I can get it. NBD