Displaying the "Last Modified" Date

Rather than looking in the properties to see when a workbook was last saved and then storing it somewhere in the workbook, I store the date and time in the workbook when it is saved.

Private Sub Workbook_BeforeSave(ByVal SaveAsUI As Boolean, Cancel As Boolean)
Cancel = False
Worksheets("Main").Range("Date_Saved") = Format(Now, "mm-dd-yyyy")
Worksheets("Main").Range("Time_Saved") = Format(Now, "hh:mm AM/PM")
End Sub

Note that this code needs to be stored in 'ThisWorkbook'

Rather than looking in the properties to see when a workbook was last saved and then storing it somewhere in the workbook, I store the date and time in the workbook when it is saved.

Private Sub Workbook_BeforeSave(ByVal SaveAsUI As Boolean, Cancel As Boolean)
Cancel = False
Worksheets("Main").Range("Date_Saved") = Format(Now, "mm-dd-yyyy")
Worksheets("Main").Range("Time_Saved") = Format(Now, "hh:mm AM/PM")
End Sub

Note that this code needs to be stored in 'ThisWorkbook'

I use the VBA function FileDateTime(PathName As String ) where pathname is the path\filename

Sub LastSaved()
If ActiveWorkbook.path = "" Then
MsgBox "Active Workbook has not been saved"
Else
MsgBox FileDateTime(ActiveWorkbook.path & "\" & ActiveWorkbook.Name)
End If
End Sub

Kim, if you see my comment from August 12, I give a better solution to the Left issue. If you want the time, then just use sLMD = Format(sLMD, "dd/mm/yy h:mm:ss AM")

Hi --

I noted that the setting of 8 characters for the LMD in the original code cut-off part of the date (giving, for example, 10/3/201, leaving off the "3" from the year). I extended it to an excessive 25 characters which gives me both the date and the time.

Also, I wanted to be able to see this on some of my workbooks, but not have it printed in the headers, so I set it up to put the date/time in cell A1, usually an empty location in my workbooks.

The resulting code follows:

Sub LastSaved()
Dim sLMD As String

On Error Resume Next

sLMD = ActiveWorkbook.BuiltinDocumentProperties("Last Save Time")
If Err = 440 Then
Err = 0
sLMD = "Not Set"
End If
sLMD = Left(sLMD, 25)
Range("A1").Value = "Last Saved: " & sLMD
End Sub

Thanks -- this was a great tip! When developing new reports for the department, there are often multiple versions.

Kim

Interesting side note, MyHeader1 actually gives me a time once an AutoSave has been created. MyHeader2 will only work once the file has been saved for real.

@jws500 I think it's fairly common practice to use Err <> 0. The only reason why you would use something else is if you wanted to trap multiple errors in different ways. A lot of times if I know there is one type of error I will encounter, I will trap it and then have an Else condition which pauses the macro for any other error. That way if there's some error condition I never knew could happen, I can deal with it when I get there (this is obviously more of a debugging solution, not something you'd want to distribute).

As for Allen's use, I don't understand the point of the Err = 0 line. I don't think it does anything, and if it does, I don't think it changes anything about the execution of the rest of the macro. Also, using the left portion of a date string is a terrible way to do it. 1/1/2013 has 8 characters, but 12/12/2013 has 10, and your macro won't work. You should use the Format function instead.

I think in this case a better way to handle it would be:

Sub MyHeader1()
Dim sLMD As String

On Error Resume Next
sLMD = ActiveWorkbook.BuiltinDocumentProperties("Last Save Time")
On Error GoTo 0

If Len(sLMD) = 0 Then
sLMD = "Not Set"
Else
sLMD = Format(sLMD, "d/m/yyyy")
End If

ActiveSheet.PageSetup.LeftHeader = "Last Saved: " & sLMD
End Sub

It's probably not the best way, but it's cleaner and easier to understand.

There's also no reason why you couldn't add appropriate error handling and formatting to the second macro as well (although with the above fixes in place, the second macro is just redundant, aside from its cryptic and limited teachings about creating a FileSystemObject).

Thanks for a useful tip. I've done something similar, but without the error checking. I will add error handling to my macro.

Question: Is there a reason you test explicitly for a single error number rather than something like:
If Err <> 0 Then