Can anyone tell me why you can type non-dates into baseline date fields and non-durations into baseline duration fields in MS Project 2010? I do a fair amount of programming to MS Project, and it should be known that when you delete a baseline date, it isn't really gone. In the backend, it stays to whatever "real" date it last had regardless if you remove it or overwrite it with a non-date value.

In MS Project 2007, it validated the date/duration and would not allow it. Not sure what 2013 does..

Really looking forward to responses on this one!



Thanks

With the introduction of Manually scheduled tasks the Baseline fields (as well as Start, Finish, Duration) will accept text entries. The Baseline estimated Finish field only accepts date/time data.

Not a bug - by design.

Thanks for your post. I didn't notice the Baseline estimated dates until you mentioned it. Not a bug, but an interesting design. Looking at the documentation it says that for automatically scheduled tasks, the values in the Baseline Start fields and the Baseline Estimated Start fields are exactly the same; unfortunately they are not as you can still have text in one and not the other.

Oh well, moving on.

If you save a baseline through the usual route, the "usual" Baseline fields will match the Estimated Baseline fields for auto scheduled tasks. You are correct, you can alter the data in the Baselines (including Estimated) as you always have been able to. I believe the baselines can be "locked" against alteration in the Project Server - not just client however.