A user has a folder he doesn't recall creating in his Outlook desktop software and wanted to know how to find the folder's creation date.
The first sample uses PowerShell, with the folder name and creation date in the PowerShell ISE window and in a message box. (You don't need to use both and can delete the method you don't want to use.)
PowerShell may be easiest for most users because you don't need to change macro security settings in Outlook.
clear $PropName = "http://schemas.microsoft.com/mapi/proptag/0x30070040" $olApp = new-object -comobject outlook.application $oFolder = ($olApp.ActiveExplorer()).CurrentFolder $oPA = $oFolder.PropertyAccessor $value = $oPA.GetProperty($PropName) write-host $ofolder.name `n$value write-host [System.Windows.MessageBox]::Show($ofolder.name +"`n"+ $value, $ofolder.name)
Get Folder Created Date using VBA
This is the VBA code needed to get the folder creation date. Because you need to change Macro security settings the PowerShell method is easier to use, unless you are already using macros.
Public Sub ShowCreatedDate() Dim ofolder As Outlook.folder Dim propertyAccessor As Outlook.propertyAccessor Set ofolder = Application.ActiveExplorer.CurrentFolder Set propertyAccessor = ofolder.propertyAccessor MsgBox ofolder.Name & vbCrLf & _ "Created at: " & propertyAccessor.GetProperty("http://schemas.microsoft.com/mapi/proptag/0x30070040") Set ofolder = Nothing End Sub
Using PowerShell Scripts
To use PowerShell scripts with Outlook, start typing PowerShell on the start menu and open Windows PowerShell when it comes up. Windows PowerShell ISE has a script pane at the top, which is useful if you want to edit the script.
Paste the entire script in the PowerShell window and press Enter or the Run button if using PowerShell ISE.
Note: PowerShell scripta will not work with the Windows Store version of Office. You'll need to use a VBA macro version if you have the Windows store version of Office installed.
Saving PowerShell Scripts
If you want to save the script as a .ps1 file, paste it into Notepad and save it with the extension .ps1. To open it in the PowerShell IDE, type powershell on the start menu and click on Windows PowerShell IDE when the PowerShell app is found. Paste the script in the editing window.
To use it, you need to allow local scripts by running this command:
To run your saved .ps1 file, right-click on the script and choose Run with PowerShell.
How to use the macro on this page
First: You need to have macro security set to the lowest setting, Enable all macros during testing. The macros will not work with the top two options that disable all macros or unsigned macros. You could choose the option Notification for all macros, then accept it each time you restart Outlook, however, because it's somewhat hard to sneak macros into Outlook (unlike in Word and Excel), allowing all macros is safe, especially during the testing phase. You can sign the macro when it is finished and change the macro security to notify.
To check your macro security in Outlook 2010 and newer, go to File, Options, Trust Center and open Trust Center Settings, and change the Macro Settings. In Outlook 2007 and older, look at Tools, Macro Security.
After you test the macro and see that it works, you can either leave macro security set to low or sign the macro.
Macros that run when Outlook starts or automatically need to be in ThisOutlookSession, all other macros should be put in a module, but most will also work if placed in ThisOutlookSession. (It's generally recommended to keep only the automatic macros in ThisOutlookSession and use modules for all other macros.) The instructions are below.
The macro on this page should be placed in a module.
Open the VBA Editor by pressing Alt+F11 on your keyboard.
To put the code in a module:
- Right click on Project1 and choose Insert > Module
- Copy and paste the macro into the new module.
More information as well as screenshots are at How to use the VBA Editor