Thread: [Solved] Strange behavior with Word macro
View Single Post
 
Old 06-03-2022, 02:27 PM
Charles Kenyon Charles Kenyon is offline Windows 10 Office 2019
Moderator
  
Join Date: Mar 2012
Location: Sun Prairie, Wisconsin
Posts: 9,470
Charles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant future
Default
Quote:
Originally Posted by Ulodesk View Post
That's it precisely.
It has been so long since I created the macro, I don't recall the Createdate field; it seems to used to be InsertDate, but perhaps it was just Date. How the field in my macro got changed from the original is an interesting question -- or not; MS update, perhaps? I'll probably never know.

Thanks for the help!
AFAIK MS has not messed with the date fields in 20+ years. If the name of your macro is InsertDate it is probably an intercept macro. Intercepting events like Save and Print. What I have done for more than 20 years is simply create templates that have the CreateDate field in them.
Reply With Quote