Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Gerhard Fiedler wrote: > Not always. "Program Files" is not guaranteed to be "PROGRA~1", it could > just as well be "PROGRA~2". > > You have to parse the output of something like "dir /x" or use some API > call like GetShortPathName or FileObject.ShortName of a file object in > FileSystemObject to find out what the short name associated with any long > name is. Exactly -- you got the idea, just apparently the way I was trying to present it needed work. I pasted in the output from /my/ "dir /x" command to illustrate, and on my system Program Files happens to equate to PROGRA~1 (as it does on most systems I've seen, YMMV). Once those equivalents have been established, they don't change unless you change the long name. To Bo's issue, you can use these equivalents with scripts that don't handle long names properly. It's not perfect, but seems to be a reasonable workaround since I would imagine we won't have much influence over the folks in Redmond. You can also have a "Program Files" for all MS-like apps and "Apps", "Progs", or something similar for all others. that's what I do, but cvsnt is still under "Program Files" and I use "progra~1" where necessary. Regards, -- Glen Starrett