>I'm not sure why you're trying to detect DST, but it shouldn't be necessary.

As far as my other reply to this, I wouldn't need to calculate an offset number of hours/minutes from the server data time if I use the approach mentioned by Viv in message #1539633. As, if the server time is also set to be associated into a property for the offset number of minutes from GMT, based on the approach in that message, then I have both offset number of minutes from two locations and I can then get the difference so to show the date of the server data into the user's local time. So, yes, in that case, if I can make it work, local DST wouldn't need to be supported. I have it presently as I haven't completed my tests. But, once I complete all this, I am pretty sure this will be simplified as is. Up until now, our applications were relying on the Member table where the member can adjust as per his timezone and if that timezone supports a Daylight Saving Time or not. So, based on that, I was able to show the proper date values where it applies. But, on some other applications, we do not want to rely on that and rely directly on the PC's settings.