# Date & Time Format Issues **URL:** \ **Category:** Ask for Help\ **Created:** [December 21, 2022, 8:25am UTC](https://community.glideapps.com/t/date-time-format-issues/55931 "2022-12-21T08:25:36Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [December 21, 2022, 10:55am UTC](https://community.glideapps.com/t/date-time-format-issues/55931/11 "2022-12-21T10:55:09Z")
If you’re allowing users to enter dates as strings, then that is just asking for trouble. My first bit of advice would be to avoid that if possible, and use a date picker. If you don’t want to do that, then my suggestion would be to use a math column to convert the entered “dates” to integers, and then work with those. Use the following: ```auto Year(Date) * 10000 + Month(Date) * 100 + Day(Date) ``` The math column seems to be pretty good at dealing with dates as strings, so you might have better success with that. The last thing I would use in this situation is the Format Date column. I gave up on that many many months ago, and I just don’t use it at all now. I wrote a bit about why below: > [@Time Format](https://community.glideapps.com/t/time-format/50074/8): > > The other thing you need to do is test it at different times of the year. Early on, when I was trying to use it, I found that it would sometimes get the day and month mixed up, but only under certain circumstances, and only if the date was ambiguous. For example, today is September 25th. In the US, they write that as 9/25/2022. In the real world, we write it as 25/9/2022. But either way, it’s obvious that it’s September 25. It can’t be anything else, because there is no 25th month. But, le… --- _[View the full topic](https://community.glideapps.com/t/date-time-format-issues/55931)._