Hi y'all,
Following up on a previous post on a topic akin to kicking the bricks with one's bare feet - does no good at all to complain about it since there is apparently nothing to be done about it. The topic: Versamail displays an annoying parenthetical suffix containing the time in the Exchange time zone forall entries created in Outlook and sync'd down to the Treo via Exchange Activesync if the Exchange server and Outlook/Treo are in different time zones (e.g.: "Lunch meeting at the Brown Palace (3pm EDT)"). Possible solution: Datebk6! Unfortunate result: the real-time nature of the push connection between the Treo's calendar and the Exchange calendar apparently causes some problem for Datebk6. Once running, Datebk6 came up with an error the first time something attempted to be pushed to the calendar. It said to delete the preferences file and try again or notify pimlico. I deleted the preferences file, but then Versamail had been blocked from updating the calendar, so I had to sync manually to get the calendar update. Sorta defeats the purpose of the push connection. There is apparently some conflict between what Datebk6 does with the calendar DB and what the push synchronization does with it. Ah, well. Though it hurts me to say so since I admire the company and the author, I have never had good luck with the Datebk<n> programs. In this case, I was hoping it would (or could be set to) just omit the suffix where the time zone of an appointment differed from the time zone of the Treo, but this conflict wouldn't allow changes to be pushed to the calendar while Datebk6 was running, so I don't know if it does that or not! Cheers, Don [Non-text portions of this message have been removed]
