On Mar 27, 2007, at 00:22 UTC, Steve Upton wrote: > >Well, you can give it exactly the final folderitem you want it to be > >(make destFile the actual file rather than a directory). > > yeah, thought about this one, but actually want it to work with the > original file name...
You can have it do so, just by constructing the destination filename using the original filename and the destination directory. But that gets us right back to your other issue. > Here's the actual path information: > > Original filename: CX default cal 9_16_05-4270D40.icc Filename in RB > : CX default cal 9_16_0#7B558.icc As viewed with what? .Name? .DisplayName? .AbsolutePath? Something else? > It copies over just fine but, as you can see, I don't have access to > the correct file name, so I can't directly access the file. I can > hunt through the folder using .item, etc but I want something that's > going to work in general use. dir.TrueChild(f.Name) should work just fine; it always has for me (and yes, I've tested it on long filenames). Is this some unusual file system? Not HFS+? A network drive? > I'll try TrueChild but I don't think that's the issue do you? No, that was a minor side-point. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
