D
dbeavon
Guest
Bob, I would recommend that you plan on having the coders work on this either way. The problem is that ABL programs often use TODAY and TIME. It sounds like your intention is that these would be impacted by the timezone (a user preference). But ABL programs frequently use TODAY and TIME in the cases where they need absolute/chronological timestamps as well. It is unlikely that the ABL programmers made a distinction between the places where TODAY/TIME were representative of an arbitrary timezone (based on the user preference) and the places where they needed to represent absolute/chronological time. Long story short - you might end up with timestamp data in your database that is an unwieldy mixture of arbitrary and totally unqualified timezones. Progress OE didn't even have the DATETIME-TZ (or even DATETIME) data type in the database until relatively recently; so even well-meaning programmers were pushed into very bad programming practices where timezones are concerned.
Continue reading...
Continue reading...