# Fixing timezones with Google sheets (not glide tables)

**URL:** <https://community.glideapps.com/t/fixing-timezones-with-google-sheets-not-glide-tables/65119>\
**Category:** Ask for Help\
**Created:** [August 17, 2023, 9:46am UTC](https://community.glideapps.com/t/fixing-timezones-with-google-sheets-not-glide-tables/65119 "2023-08-17T09:46:23Z")\
**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:** [August 17, 2023, 10:06am UTC](https://community.glideapps.com/t/fixing-timezones-with-google-sheets-not-glide-tables/65119/4 "2023-08-17T10:06:07Z")

</div>

That’s the problem with it. It works perfectly fine probably 99.99% of the time, and lulls you into a false sense of security. But when you get bitten by that 0.01%, it hurts (and makes your head explode).

Below is a bit of a rant I had about it last year.

> [@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/fixing-timezones-with-google-sheets-not-glide-tables/65119)._
