You missed my point he

There are lots of cases where I open a file as readonly--not because I don't
want to save my changes, but because I want to protect the existing workbook.

Precisely. Read only is read only. No saving, because there's no changes.

My point was that I want to save my changes to a different workbook.

And I (and I think most people) appreciate that warning.

But maybe MS will agree with you in a future version.


Aaron Oxford wrote:

Bah, we are going nowhere. But to finish the discussion.

"Dave Peterson" wrote:

There are lots of cases where I open a file as readonly--not because I don't
want to save my changes, but because I want to protect the existing workbook.

Precisely. Read only is read only. No saving, because there's no changes.

I want to make tons of changes and then save as a new name. By opening the
existing file as readonly, I know that I won't screw that one up.

And if I weren't prompted, I may forget to save as the new name.

It seems like a very reasonable approach to me.


Basically it comes under the heading of dialog fatigue. If Excel bugs me to
save changes whether or not they've occurred, I might tell it not to save as
usual when in fact I wanted to this time. If I forget to save changes because
I forgot, that's my problem. If I automatically answer that annoying dialog
box the way I always do and lose changes I was making, *then* I blame Excel
for my loss.

Thanks for the discussion, maybe someone at MS will take it into account for
the next version.

--

Dave Peterson