Default save on exit for ppt should be 'do save' not 'don't save'

[Guest]

when you exit most MS programmes you get a prompt 'do you want to save
changes'. Usually this defaults to 'yes' so you hit enter to save before you
exit and lose the changes. Strangely, with powerpoint, it defaults to 'no'.
I've now lost count of the number of times I've lost changes by just hitting
'enter'. Most times I exit I will want to save changes I've made, so this
should be the default. At the very least all MS products should be
consistent, whichever way.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...a-b6db3bbb5e14&dg=microsoft.public.powerpoint

 

[Ute Simon]

when you exit most MS programmes you get a prompt 'do you want to save

changes'. Usually this defaults to 'yes' so you hit enter to save before you
exit and lose the changes. Strangely, with powerpoint, it defaults to

'no'.

I don't know whether you'll read this reply at all, or which version of
PowerPoint you use. But in my PowerPoint 2003 (German), it defaults to yes,
as it should.

Kind regards,
Ute

 

[Michael Koerner]

Does for the English version also. This may have been one of the glitches
fixed with the release of SP1

--
<>Please post all follow-up questions/replies to the newsgroup<>
<><>Email unless specifically requested will not be opened<><>
<><><>Do Provide The Version Of PowerPoint You Are Using<><><>
<><><>Do Not Post Attachments In This Newsgroup<><><>
Michael Koerner [MS PPT MVP]

 

[Guest]

Hi,

this happens in Powerpoint 2003 SP2, too, and I do not believe it is to do
with the version: The very same powerpoint installation defaults to "yes"
with one presentation and "no" with another. The "no"-presentation keeps that
behaviour on a different computer, and it turned out that it was created
using a different template than blank.pot. So it is likely it has something
to do with the template it stems from, but we aren't any closer then that to
a real solution either. Maybe this points a direction though.

Chris