Insert date and time in Word

Doug,

If I set my long date format to DDDD, MMMM dd yyyy in Region & Language Settings, then Word shows Wednesday, December 05 2012 in the Insert Date & Time dialog.

If I set my long date format to DDDD, MMMM d yyyy in Region & Language Settings, then Word shows Wednesday, December 5 2012 in the Insert Date & Time dialog.

That works as I expect it would with US English selected as the language.  For me at least, it appears the long date format in Date & Time dialog is dependent on region settings long date format.

I don't have a clue why the OPs doesn't work that way as well.  Maybe like you, the northpaw has multiple languages involved.

I'm curious to see what the result of the macro is.

The code in the UpdateAllFields routine on Greg's website is just being used as an example.

What you need to do is copy the

Sub DateLongStamp()

'Inserts current date

Selection.InsertDateTime DateTimeFormat:="dddd, MMMM d, yyyy", InsertAsField:=False

End Sub

and paste it into the Visual Basic Editor.

See the article "What do I do with macros sent to me by other newsgroup readers to help me out?” at:

http://www.word.mvps.org/FAQs/MacrosVBA/CreateAMacro.htm

Of course I have no idea what you have done to create Macro1 through Macro5.  If they aren't being used then delete them.  Maybe you will have more success with the QuickMethod:

Installing Macros (QUICK METHOD):

There is almost always more than one way to skin a cat. The basic method should be fool proof, but as you gain familiarity with the VBE you will discovery other methods. I typically bypass the "Macros" dialog (ALT+F8) altogether and go straight to the VBE using the shortcut ALT+F11. From there:

• I locate and select the project in Project Explorer.
• Use the VBE "Insert" menu to insert a new standard module.
• Select the new module and use the Properties Window "Name" property to give my new module a meaningful name (e.g., I often name my modules modMain).
• Paste my procedure into the main code pane.
• I then immediately step through the new procedure using F8 or run the procedure using the VBE toolbar or menu commands.

Greg, I got as far as: "Then copy UpdateAllFields procedure shown above and paste it in the VBE code pane below the Option Explicit statement (if present)."

But the top right hand corner doesn't read UpdateAllFields instead it says: (Declarations) and the drop down arrow brings Macro1 Macro2, Macro3, Macro4 and Macro5. One of them is probably my AutoCorrect Utility which I use. The newest is Macro5:

'Macro5 Macro

' DateLongStamp()

Now what?

I wonder if I just change the “MMMM d, yyyy”, False, to read “MMMM d, yyyy”, True? Would that do it?

It is highly unlikely that you will screw it up. The downside would be directly proportional to the degree of screw up as highly as unlikely as that is.

IMHO Word is like a Maserti.  Those who elect not to use macros keep it in first gear.

 

 

Unfortunately, I cannot replicate your issue in any version of Word (2003, 2007, 2010) under Windows 7. Note that your original question still doesn't say what version of Word or Windows you have; you can edit your post to correct this.

Okay Suzanne I just edited my original post per your suggestion.