>>Thanks, I agree that the upper case filenames are extremely annoying, I did not know that there is a difference with the putfile, I thought this was managed by VFP when it receives the output. But of course that makes sense, I will probably then also use the better method in the future.
>
>Not just annoying but actually a problem in some cases. I remember once on a project we were using a SVN based version control system, which sat on a *ix based system, where the filename is case sensitive. We had serious trouble with VFP just deciding to save a file in a different case - perhaps preserving the stem but uppercasing the extension. I had to write some serious code to consolidate things before submitting to the repository, or else we'd have had chaos.
>
>Now I'm keeping lots of my files on a Samba share (well not exactly Samba, it's a shared drive of the host for a W7 virtual box) where the filesystem, being a linux thing, is case sensitive. I've had issues with certain folders because some of them would be scanned (in my screen savior app, see downloads) multiple times. Eventually found there were two such folder, one called "...\some stuff" and the other "..\Some Stuff". Which are ok under linux; when VFP sees them it still sees them one at a time (in FSO's oFolder.SubFolders collection) but then looks it up in the table lowercased - because I didn't foresee this, having initially developed this for a filesystem managed by Windows, so decided to ignore the case. Mind you, the filesystem on that drive is actually NTFS :).

I have the same problem using SVN, not because of the GetFile dialog, but when editing table structure or compile menus etc it would change the case of the files. For this I try to adapt the case of the files to the same as it gets created but it seems to be sometimes erratic.