OK suspicions confirmed - Autorecover does NOT recognise VBA changes.

My excel has just crashed again but since my first post I had inserted
=now() on the front page of the macro store.

This volatile field is all that autorecover needs.

"Gizmo63" wrote:

OK - not a happy bunny!

I have just lost a very productive 1½hrs work because the autorecover
function does not 'see' the changes made in VBA.

To centralise the macros used around my teams workbooks I have a 'store'
workbook that contains nothing but macros. Hence, when developing the macros
I am working behind the scenes so to speak.

I know all about "saving your work regularly" but time flies when your head
is down and the keys are being hammered and it's easy to lose track of how
much has been done.

I am guessing that the autorecover failed because nothing had been changed
on the spreadsheets.

Microsoft - - please give us back the Autosave function!

autorecover is a nice idea but is not infallable (sometimes scrambles
recovered files too)

Not happy and going for a walk - grrrrrr!

Have a nice day now.

----------------
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/comm...lic.excel.misc