# Relation will recognize a date match but not Query

**URL:** <https://community.glideapps.com/t/relation-will-recognize-a-date-match-but-not-query/74796>\
**Category:** Ask for Help\
**Created:** [July 10, 2024, 5:58pm UTC](https://community.glideapps.com/t/relation-will-recognize-a-date-match-but-not-query/74796 "2024-07-10T17:58:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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:** [July 11, 2024, 9:29am UTC](https://community.glideapps.com/t/relation-will-recognize-a-date-match-but-not-query/74796/4 "2024-07-11T09:29:40Z")

</div>

The Format Date column is the work of satan. It will work perfectly 99.9% of the time, but that 0.1% when it breaks will do your head in. I do not use it, and I do not recommend using it.

The Math approach is a little more work, but is 100% reliable.

For more about why I don’t recommend the Format Date column, see 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/relation-will-recognize-a-date-match-but-not-query/74796)._
