Thank you for all your replies and suggestions.
In response to the various posts:
Eric - I would suggest it is a bug - it is surely not deliberate and if so I
would say that is wrong and should be optional.
I think a posting to the MS bug report site would be appropriate.
However your API solution is obviously the way to go to get around
I changed my reference from BT :) sorry.
Trey - I would never use a scripting object as this is subject to whether
scripting is installed on the target system,
and could possibly be affected by whether script blocking is
installed e.g. Norton Antivirus?
Anders - Just because windows is not case sensitive it does not mean the
rest of the world is not.
I need to have the original case of the filename preserved because I do
multiple file copies then zip them into one file.
This one file then gets ftp'd to Unix server which then unzips the files
but hey they are now case sensitive and invalid!
And all because FoxPro has changed the case the process fails.
Obviously there are more steps and it is more complex process than this,
but this and the original post were/are simplified to demonstrate the
actual problem for the purposes of this post).
Don't be too quick to judge what other people do and deal with the
This is my second post relating to case sensitivity issues - my other was
many months ago on another issue.
I think that file name case sensitivity can be an important issue when
moving files around the WWW on
servers that are not run by Microsoft software e.g. Unix/Linux.
Thanks for your suggestions
Post by BT
I have a problem in VFP8 SP1 using the "copy file" command.
I am trying to copy a file to a different folder with exactly the same name
and in the same case.
copy file c:\test\MyFile.txt to c:\test2\MyFile.txt
Everything works find except the new file in the folder c:\test2 actually
now has the filename myfile.txt
Thus the name of the file is being converted to lower case, loosing the
capital M and F.
This causes me further problems as I need the name of file to remain in the
same case as the source.
I am running on Windows XP SP 1 with all the latest updates and the disk is
in NTFS format.
I can easily rename the file in explorer to the correct case but need this
to work directly from Foxpro copy file command.
Is this is a bug?
Is there a workaround?
Is there an alternative set of code that will do the copy correctly?
Thanks for any help.