[whpalmer4]

I think solution is perhaps a bit more praise than it deserves, I'd call it a workaround :-) Maybe one of the OmniPlan developers will enlighten us about why this situation is the way it is...

[Adelus]

Originally Posted by whpalmer4

I think solution is perhaps a bit more praise than it deserves, I'd call it a workaround :-) Maybe one of the OmniPlan developers will enlighten us about why this situation is the way it is...

Good morning,

I see your point, after editing the date once again (honest, I'm being careful!) and then watching a beachball try to figure out 23/12/200 .... I guess I was really behind in my schedule that time!

I think I'd prefer it if OmniPlan waited for me to exit the field before parsing the date, and if it just plain didn't accept 3- or 5-digit years, that would be good too...

Anyway, now that I know what's happening I can slap my forehead and force quit with relative calm.

Thanks again, whpalmer4. Whatever this season means to you, may it be filled with joy.

Adélus

[skwirl]

Apologies for the bug with entering dates. We have a bug report written up in our database and will be taking a look at it.