Windows 2003 / UniVerse 10+ We recently expanded into a different time zone! Our server time is syncronized to pacific time (daylight savings or not). Now we have electronic timecards as well as many other entry processes being performed in a Mountain Time Zone.
Of course all of the processes continue to show Pacific Time: on the timecards and delivery times reported to customers. I suppose there is no easy fix for this? Shortsighted maybe, but we've been happy for 55 years in a single time zone! Does anyone have any suggestions for us? We also have drivers who cross time zones now...will clock in at one time zone and clock out in another. I'm just wondering how others might handle UniVerse / SB+ applications across zones, especially since all processes were built with only one timezone in mind. Thanks for any and all suggestions! Nancy Fisher [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
