According to M. Pietrse, it's "an unwanted sideeffect caused by a bug in the
VBE"...
There is an easy way around it, though: Simply create a short sub in the
workbook you want to save

Sub SaveMe()
ThisWorkbook.Save
End Sub

and call that to save the workbook.

Thanks to both M. Pieterse and M. Ogilvy for your help!

Bruno

"Tom Ogilvy" wrote in message
...
I would drop him a line to make sure. This sounds like a flaw he would be
most interested in fixing.

--
Regards,
Tom Ogilvy


"Bruno G." wrote in message
...
Thanks for the input... Hadn't thought of that...
But no luck, if I dismiss the prompt on closing, my changes are lost...

Found it! The problem is caused by an add-in: AutoSafe by JKP
Application
Development Services (http://www.jkp-ads.com/Download.htm) - If I uncheck
it
from the Add-Ins dialog, the save command works instantly in VBE...
Guess
I'll drop him a line about it but I think he'll see this one...

Bruno

"Tom Ogilvy" wrote in message
...
I am not sure that checking directly is reliable. Excel works on a copy
of
the file. I would make changes, save, then exit and choose not to save
in
response to the prompt. Then see if your changes were retained.

--
Regards,
Tmo Ogilvy

"Bruno G." wrote in message
...
Of course, it would help if I told you I'M using Excel 2002 SP3 on
Windows
XP SP2...

"Bruno G." wrote in message
...
Hello!

There is something strange going on...
When in the VBE, if I edit the code in one of the workbook in my
XLStart
folder, the Save command doesn't work... I don't get any errors or
messages, but if I then close Excel I get a prompt to save the file.
I
checked the file directly, and indeed, after the Save command, its
timestamp does not change. So now when I make changes in these
XLStart
files, I have to exit Excel to make sure the changes are saved...
Quite
annoying...

Anybody as a suggestion? Is this by 'design'?

Thanks
Bruno