View Single Post
No, T-zero is pretty much defined to be the project start date and there's no way to disable violations. In think in your case I would recommend just representing that milestone as a good old fashioned milestone and let it fall on T-WhereItMay.

Since moving day is really fixed but you don't know when, I suspect you will be wanting to schedule from that milestone back in time with some tasks taking place as late as possible. At present, OmniPlan is focused on shortening the project only from the end. Scheduling as late as possible given other constraints is something we hope to add. Given that, I think I would suggest _not_ putting start/end constraints or a fixed date on the milestone for now.