We've found that this is really a MS problem that has to do with a library member that is linked into all version up until Ver 9.
It has to do with the regional settings and the way in which the routine converts from GMT to local REGIONAL time.
One workaround is to turnoff regional on the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.