Within picoBeat, tasks and events are considered very different objects with different properties, and are stored in two separate databases. While this is how most phones and PIM software work, there are a few devices out there that consider that tasks and events should be stored and moved around together. This is a problem for synchronization as those phones will send all updates for tasks and events together while picoBeat will expect to synchronize them separately against two distinct database.
To get around this problem picoBeat now has a new virtual database available for synchronization called “caltasks”. It will synchronize both tasks and events at once by presenting what looks like a single database to the phones who work that way.

Thank you! It makes syncronization much easier.
However, I’ve encountered a new problem. If I create an appointment on my phone, it appears one hour earlier on the server. The other way it works alright, so if I create the appointment on the server, no shifting occurs. I am from Budapest, GMT+1 and I have this setting both on my phone and on the server.
Comment by RiBBiT — December 8, 2009 @ 1:04 pm
The problem appears to be that your phone displays time in local time but sends it in UTC (GMT+0), whereas picoBeat works in and expects local time.
I have corrected the problem by converting automatically all times marked as UTC by the phone to local time, and it seems to work OK with the Nokia emulator. This should be corrected with all databases (caltasks but also cal and tasks).
Comment by Pierre — December 8, 2009 @ 3:48 pm