Me.Saved not working

[jomili]

I have this in the ThisWorkbook module:

Please Login or Register  to view this content.

In Excel 2003 it always convinced Excel that the workbook was saved, so no save prompts appeared. Now in 2010 the code doesn't appear to be working, because I'm getting the "Save" prompts again. Is there updated code I could be using instead?

[jeffreybrown]

See if this works for you...

Please Login or Register  to view this content.

[jomili]

Jeff,

Thanks, but you missed the point. The workbook is opened so that changes can be made to it and saved elsewhere under another name, but when the original template is closed I don't want any changes saved to it. The "Me.Saved" used to convince Excel that the workbook had ALREADY been saved, so there was no prompt to save changes.

[JosephP]

the code is the same in 2010. do you have any application-level event code?

[shg]

Why not just make it read-only?

[jomili]

Good question. I set it up about two years ago, and I know there was a reason I didn't make it read-only, but the reason escapes me now. But I've noticed that other workbooks that I've set up with "Me.Saved" are also prompting for a save when closing. It's been only a minor annoyance, not a problem, but now it's happening with my bread and butter application.

[JosephP]

have you tested that the event is actually being triggered? I like to add a debug.print to events that don't do anything obvious.

[royUK]

I think you've missed the point of templates, you save them with the xltm extension then you cannot overwrite a template. xltx for non-macro templates

[jomili]

Roy,

I think you may have hit on something I HAVE missed. When I mentioned "template", basically what I'm talking about is a workbook filled with a bunch of code and pre-formatted worksheets. When my main tool runs, it opens my "template", and pulls data from about 20 other workbooks to fill it, then saves it 15 different ways, then shuts it down. I THOUGHT, when I started this post, that that was the one that was giving me the problem. It wasn't. BUT, I never thought of saving it as a Template rather than a Workbook; would that give me any benefit?

By the way, the real culprit giving me the error message didn't have the Me.Saved code. It's closed by this routine:

Please Login or Register  to view this content.

So, it may be that the "ActiveWorkbook.Close False" isn't working the same as it did. I've added the Me.Saved code, and will try it out again tomorrow morning.

[shg]

You realize the last line of code will never execute?

[jomili]

You mean the 'Activeworkbook.Close False' line? It worked just fine in 2003, but sure doesn't appear to work in 2010.

[shg]

The active workbook (and all other) gets closed because you quit Excel with the prior line.

[jomili]

When I was setting it up (in 2003) if I closed the activeworkbook first, the application never quit. Moving it below the Application.quit closed the workbook without requesting to save changes, and closed the application. I just tried moving that line, closing the Activeworkbook first; Excel never closed.

[shg]

If you close the workbook containing the running code, or quit the application, the last line to execute is whichever line did one of those things. How could it be otherwise?

[jomili]

So then, I guess what you're telling me is that the line

Please Login or Register  to view this content.

has no value because the Application.Quit will take care of closing it anyway? Maybe that's why I had the Me.Saved in it in the first place.

[shg]

Yes. If you quit Excel, how could the workbook be running?