O
Oliver
Hello,
I am writing an application that will be used across multiple time zones
(Eastern to Pacific) and since much of the application revolves around time
stamps, I need a best practice for storing time information in a database
and displaying it correctly to the user (adjusted for his respective time
zone). I have been thinking about using UTC and adjusting everything when I
output it, but then the user cannot use the native data in the database
(e.g. for reporting services).
Is there any elegant way to do this (my dream would be a session-specific
time zone setting that will adjust all date to string and string to date
functions). Anybody had a similar problem?
I CANNOT SAY HOW MUCH YOUR HELP WILL BE APPRECIATED
Oliver
I am writing an application that will be used across multiple time zones
(Eastern to Pacific) and since much of the application revolves around time
stamps, I need a best practice for storing time information in a database
and displaying it correctly to the user (adjusted for his respective time
zone). I have been thinking about using UTC and adjusting everything when I
output it, but then the user cannot use the native data in the database
(e.g. for reporting services).
Is there any elegant way to do this (my dream would be a session-specific
time zone setting that will adjust all date to string and string to date
functions). Anybody had a similar problem?
I CANNOT SAY HOW MUCH YOUR HELP WILL BE APPRECIATED
Oliver