Summary: This page contains the list of known issues encountered when porting an application using the Pocket Outlook Object Model to Windows Mobile 5.0 from an earlier Windows Mobile version

*All day appointments - All day appointments were formally saved as zero-length appointments but starting with Windows Mobile 5.0 are now stored as 24 hour appointments
*Prior to Windows Mobile 5.0 an all day appointment on a given date such as 21-February would start at 12-midnight on 21-February and end at 12-midnight on 21-February (zero length)
*In Windows Mobile 5.0 it will start at 12-midnight on 21-February and run for 24 hours.

*Pocket Outlook data no longer directly accessable through CEDB/EDB interface - Prior to Windows Mobile 5.0, Call Log, Calendar, Contacts, and Tasks data were stored in a CEDB database. The Pocket Outlook Object Model (POOM) API provided access to that data. However, some applications accessed the data directly through CEDB rather than through POOM. Starting with Windows Mobile 5.0, this data is no longer stored in CEDB databases and, as a result, those applications that do not use POOM will no longer be able to access Contact, Calendar, Tasks, and Call Log data. Applications previously using POOM and the call log Documentation for the Windows Mobile APIs will run correctly on Windows Mobile 5.0.
*POOM performance has been improved and new features, such as events and named properties, have been added that address the most common reasons for developers previously by using CEDB instead of POOM.