Insert date and time in Word

Anonymous
2012-12-03T03:18:02+00:00

In Region and Language when I set the date as follows:  dddd, MMMM d, yyyy   It shows this way:  ‎Sunday, ‎December ‎2, ‎2012  Yet when I use the insert date and time in Word it comes out:  Sunday, December 02, 2012   Until this latest Windows or Vista I never had this problem. Any ideas?

I use Windows 7, Microsoft Word 2007.

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Newest
  1. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2012-12-06T03:57:49+00:00

    It appears that the way in which Word inserts the Date is dependent upon the Language selection in the Date and Time dialog.

    With English (Australia) seleted, the long date format is:

    Thursday, 6 December 2012

    With English (US) selected, the format is

    Thursday, December 06, 2012

    English (UK) gives

    Thursday, 06 December 2012

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2012-12-06T03:56:52+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-12-06T03:44:34+00:00

    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.

     

     

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2012-12-06T03:07:27+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  5. Suzanne S Barnhill 279.5K Reputation points MVP Volunteer Moderator
    2012-12-05T23:00:59+00:00

    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.

    Was this answer helpful?

    0 comments No comments