Last updated - September 4, 2001
Amiram's long days jouney into night . . . overnight and recurring events testing.
"What I did was, I entered some fake events into Outlook, synced once, and then deleted them from Outlook and synced again. I didn't risk modifying anything on the Rex and syncing back. I am using collaborative Exchange (no PST, or rather PST for old documents only), and I don't know what a restore may do to public meetings.
So, as the story goes, "my Rex 6000 arrived a few days ago". I spent some time with it, and the conclusion - it is DEFINITELY going back.
Before I return it, I plan to spend some more time and prepare a detailed description of all the cons (there aren't any pros that I could find, at least so far).
I did some basic experiments with calendar events that I entered in Outlook and synced with both Rexes. Here are the conclusions.
Event #1
Description: An event that starts at 08:30 on Friday and ends at 09:00 on Sunday. Reason for testing: The 6000 does not support events that span overnight.
Nothing whatsoever appears in the daily view of Friday and Saturday. On Sunday, the daily view shows the event at 08:30. When this event is clicked, it says "Friday, 8:30 to 23:55". Weekly view shows nothing on Friday and Saturday, and fills up the whole day starting at 08:30 on Sunday. As for monthly view, I have other appointments on Friday so I can't tell, but nothing shows on Saturday, and Sunday shows busy. It really can't get any worse (correction: Puma/Xircom can probably find a way to make it even worse).
Event #2
Description: An event that recurs every 3 weeks for 5 times. Reason for testing: The 6000 doesn't have "every 3 weeks".
The event is fanned into 5 separate events.
Event #3
Description: An event that recurs weekly for 7 weeks. Reason for testing: The 6000 doesn't have "for 7 weeks".
Sort of ok - the event appears as recurring (not fanned). It says "occurs for 2 months", but appears only at the correct 7 weeks. The R6K indicates loud and clear (when you press "modify") that this event recurs for 2 months, although actually it recurs for 7 weeks only. My guess is that it saves the event as actually recurring for 2 months and adds an exclusion for the last week.
Event #4
Description: An event that recurs weekly for 3 weeks, with the second one deleted. Reason for testing: To see how exclusions are handled.
Ok - the event shows as recurring but the second week doesn't show. Event #4, which recurred for 3 weeks, showed "recurs for 1 month."
Event #5
Description: An event that recurs weekly for 3 weeks, with the second one moved to a different hour. Reason for testing: To see how exceptions are handled.
On weeks 1 and 3, the event shows as recurring. On week 2, the original event doesn't show, and the new hour appears as a non-recurring (fanned) event." Event #5, which recurred for 3 weeks, showed "recurs for 1 month."