Wrong date when using the field:date function

Question

Original Title: "Word Feld Datum falsch"

Moderator Note: Manually merged duplicate (English) thread

Hi there,

could you help me with this:

when I insert a field for the accurate date over the insert field:date function, in some documents the wrong date is inserted.

Sincerely,

Chris

---

Hallo! Ich habe folgendes Problem: Wenn ich in Word unter "Einfügen" die Funktion "Feld" und dort "Datum" wähle, schreibt er mir seit einiger Zeit nicht mehr das heutige Datum, sondern irgendein veraltetes hin aus dem Jahr 2010. Wie kann ich das Datum für die Datumsfeldfunktion wieder richtig einstellen?

Vielen Dank!

Answer 1

The {CREATEDATE} field is the date (and time, if you specify it) when the document was created.

Read all about fields**here,**Christoph.

Answer 2

Is it possible that the fields are different? You should view the field codes (Option F9 or Word > Preferences > View > Show > Field codes) and compare them. There are several switches within fields, as well as various fields that can give you dates.

Another thing: fields are usually updated by Word. If you want a field to remain unchanged after you insert it, select it (or select the whole document) and press Command Shift F9 to convert it to static text.

Depending on your System Preferences, you may need to also press the Fn key together with F9 in the above shortcuts.

Answer 3

Yes, that solves the problem! Using the View of the field codes I detected, that I have once inserted the CREATEDATE field and once the DATE field. The DATE field uses the right date, the CREATEDATE not. What is CREATEDATE then and why does it produce any date but not the accurate?

Thank you very much,

Chris

Answer 4

I am going to ask a question about yur problem that may or may not be you issue. IF it's not say so.

Are   you using OSX.7 (Lion)?

Is you problem associated just showing two number Years  even if you have set for 4 number dates?

If so this a Bug with OSX.7 (Lion), not Office.

If this is your experience go to Apple's website Feedback/Bug request and Request a Bug fix for this problem. The more people that turn in the bug, the more likely Apple will get off there duff and try to fix the problem.