12204 Incorrect error message

[chrisjj]

If I use "Move to folder" on a file of the same name as a folder in the destination folder, BC says

The target folder already contains a file named 'test'.

even though there is no such file.

[Aaron]

Thanks for the report, Chris.

Are you able to perform the same steps using Windows Explorer? If not, what kind of error message do you receive?

[chrisjj]

Aaron, it is a simple mistake in the BC error message. "file" when the offender is in fact a folder.

[Aaron]

I've made a tracker entry for the behavior I'm seeing in office.

[chrisjj]

And that's the same as I reported seeing here?

[Aaron]

Assuming you are also seeing the same behavior in Windows Explorer that I am seeing, yes.

[chrisjj]

My report is about BC, not WE. So if you are seeing "the same as I reported seeing here", that's also in BC, not WE.

[snidely.too]

My report is about BC, not WE. So if you are seeing "the same as I reported seeing here", that's also in BC, not WE.

Note that Aaron did ask if you had tried the same copy in WE. That's not a random question, as BC uses the underlying OS code that WE uses, so it is helpful to determine what behavior is unique to BC and what is shared with WE.

/dps

[chrisjj]

Relevent only to the fix, not the problem, surely.

[Michael Bulgrien]

I would think that it would be quicker for either side to simply do the test instead of all this back and forth banter.

WE under Windows 7 says: "There is already a folder with the same name as the file name you specified. Specify a different name."

BC under Windows 7 says: "Unable to move <filepath>: Cannot create a file when that file already exists"

[Tim]

The message is coming from the OS, so it's not simply changing a string in our code. As Michael demonstrated, the message differs between Windows versions.

The suggestion is then that we build in functionality to give a more appropriate error message under older OSs. We will consider that suggestion.

[chrisjj]

I would think that it would be quicker for either side to simply do the test instead of all this back and forth banter.

I guess Support has something better to do today that test their own software. I know I have.

[Tim]

That's an unfair comment. Aaron tested this issue back on November 22nd and has made an appropriate tracker entry.

[Aaron]

Hello Chris,

I tested the error message back when you originally posted it. Since it is passed back from the OS, I was double checking to make sure that the same cause was having the same effect. So, I have a tracker entry open for :
WE error A -> Shows in BC as Error A.

As long as you are also hitting error A, then the tracker entry addresses this. If for some reason, you are hitting WE Error B -> Shows in BC as Error A, then we can't know, since you didn't have time to perform the additional tests.

I wouldn't worry. I'm guessing A -> A on your end as well; I was just trying to be thorough.

[chrisjj]

That's an unfair comment. Aaron tested this issue back on November 22nd and has made an appropriate tracker entry.

Then I see no grounds for asking the customer to test Windows.