Is there a way to disable the automatic timezoneswitch within the Notes Client?
A date field on a doc is set to 09/17/2010 in Amsterdam, when the doc is looked at in USA it is seen as 09/16/2010.
Looking to disable this so that it comes out as 09/17/2010 no matter who looks at it
Subject: dates do not have timezones…
So what you’ve got is a field containing a date and time. Get rid of the time and it’ll show the same date for everyone.
Or, use the field options to select that it should not “adjust time to local zone” (which is the default).
If this didn’t solve your problem, please describe it in more detail. See also Working with Date/Time Values in Lotus Notes.
Useful blog: Best Practice Makes Perfect
NOTE: My policy is to post only two responses to the same question. So that my second response can solve your problem rather than being a request for details, please read the C R I S P Y document.
Subject: yes I tried these things
I know the date fields do not have timezones.I guess what I should have asked is how to stop the Lotus Notes client from using the OS for what timezone it is in
Is that even possible?
Subject: You want to disable timezone adjustment entirely in the client?
You say “I tried that” but still not providing any details about what you tried or what you’re doing.
I really do know what I’m talking about. If you read the document I posted a link to, I think you will find the answer to your problem. I say “I think” because you didn’t give enough information for me to tell for sure what the problem is. But, since you say it’s a date-only field, I suspect you’re experiencing the “midnight problem”, caused by incorrect LotusScript code.
Otherwise: you want to “stop the Lotus Notes client from using the OS for what timezone it is in” because one field in one application is not behaving the way you want it to? You don’t think it would be better to figure out what the problem is with that one field?
But since you asked: by editing a location document, you can set the Notes client to behave as if it’s in a specified timezone, overriding the OS setting. Of course, this will cause confusion in the user’s calendar because the time it displays for their appointments, will not match the system time that the operating system displays or the time on their wristwatch, though I believe meeting alerts will still come up at the right times, providing the system time is right.
Based on my work with end users, I’d expect them to be resistant to reconfiguring their environment and making everything else work in a way that’s inconvenient for them, just so that your one view or form works correctly. They can be quite unreasonable that way.
Since I’ve reached my limit of two responses to this question, I’ll bow out. I hope you now have an answer that’ll work for you.