Blue Orphans, boo hoo

[dburtis2]

yes, I am copying across a network. I never have tried same copy with Windows Explorer (BC3 is soo much better!), so I can't disagree with your comment. (I didn't mean to imply that BC3 was stripping the space - only that I noticed it when using BC3 to initiate the copy).

Glad to hear BC3 does not strip spaces in name - boo to Microsoft for doing that.

[Zoë]

I found that if a file has a leading space in its name, when BC3 (noticed in Version 3.2.3, build 13046) copies it, the leading space is removed.

BC doesn't strip leading spaces, and testing here doesn't show the behavior you're describing. If you're copying across a network one of the OSs may be doing that, and you should see the same behavior copying the files in Explorer.

[dburtis2]

I found that if a file has a leading space in its name, when BC3 (noticed in Version 3.2.3, build 13046) copies it, the leading space is removed. That leads to what looks like orphans on both sides with the same name (when the folder compare is updated). If the copied side file is renamed by adding back the leading space, then BC3 says they are the same file.

[Aaron]

If the folder structure matches, then files with the same name should also align. Could you take a screenshot or Snapshot (Tools menu) of your two folders?

You can email them to us at [email protected]
Please include a link back to this forum post if you email us.

[Mongo The Challenged]

OK, I've renamed 2 files that are exactly the same in two different hard drives (folders), the files names are the same yet it shows it as blue and on different lines. Por que?
Same exact files, same exact name, but it shows them as diff, or orphany, I want them to be black and on the same line. Am I making any sense? LOL
Thanks for any help, MTC