No, I'm saying you can make a table called "Date Changes". And use that to keep track of your changes, and who (and why if wanted)
>
Just one Field;
"Date"
A second field would be needed if you had a "Why"
>
Each 'Project' can have many date changes.
>
Summarize Max Record ID
>
Pass new max RID as lookup
>
Summarize Date where max RID = Record ID#
Now you have your log of date changes with time stamps and record owner.
Much cleaner and more scalable if you have multiple dates that need to change. Also gives you much better reporting outputs. (ie. How many times this date has changes, most frequent cause of Date changes, who makes the most changes, etc.)
