Hi, John, Thanks for the quick reply.
On Mar 6, 2012, at 00:57 , John R Hudson wrote: > On Tuesday 6 March 2012 06:35:00 Justin C. Walker wrote: > > I suspect no-one has thought of the possibility that one might use the > newfile > filename (albeit in a different folder) within "Save As". Just change the > filename as well as the folder. > > I have never had this problem when saving a file with the same name to a > different folder; so I suspect this issue is confined to using newfile in > more > than one folder. I don't think that is the issue. The underlying cause may be that "newfilexxx" is not acceptable as a file name (in which case, shouldn't the documentation and warning indicate that?). I think that the error message is incorrect, or at least totally misleading. In my case, there is *no* file named "newfile*.*" on my system, and the error message doesn't claim that. It says that it's open in the current session. In fact, at the time, it is the only open file/window in the app. It's perplexing how, when I have this open and just want to save it as is, that I am "overwriting it". Feels like a bug to me. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income -------- Experience is what you get when you don't get what you want. --------
