<div dir="ltr"><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">On Mon, Jul 23, 2018 at 12:48 PM, Robert MacGrogan<span> </span></span><span dir="ltr" style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><<a href="mailto:rmacgrogan@flightbridge.com" target="_blank" style="color:rgb(17,85,204)">rmacgrogan@flightbridge.com</a>></span><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> </span>wrote:</span><br style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><blockquote class="gmail_quote" style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">It looks to me like the time zone data for America/Grand_Turk is incorrect in 2018e version of the database. </div></blockquote><div><br></div>If only there was some way to get a descriptive version string from the <span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">America/Grand_Turk he is actually using.</span><div><br></div><div>:-)</div></div>