WM 5.0: how to do a CeOidGetInfo() on a POOM oid?

[Jack]

In my pre-WM 5.0 code, I would call CeOidGetInfo() on the oids I
retrieved using POOM.

However, with WM 5.0, the same CeOidGetInfo() calls now fail.

I'm assuming that it is because the data is now stored in EDB.

Question: What is the WM 5.0 way to get more information about an oid
returned from POOM?

Also, when I enumerate the databases on my WM 5.0 device, I do not see
a database called "Appointments Database", does this database have a
new name?

 

[Peter Foot [MVP]]

The database won't show up in the CEDB object store as it's now in an EDB
volume. What particular information were you using CeOidGetInfo for? there
may be a better alternative as there is some new functionality in POOM with
WM5.0

Peter

 

[Jack]

Small tangent... not using POOM for the below...

Should CeOidGetInfo() work on Windows Mobile 5.0?

I'm asking because...

If I build for PPC 2003 and deploy on a PPC 2003 emulator, the
CeOidGetInfo() call works (without POOM).

If I deploy the same PPC 2003 build on a WM 5.0 emulator or a real WM
5.0 device, the CeOidGetInfo call fails.

 

[John Socha-Leialoha]

Small tangent... not using POOM for the below...

Should CeOidGetInfo() work on Windows Mobile 5.0?

I'm asking because...

If I build for PPC 2003 and deploy on a PPC 2003 emulator, the
CeOidGetInfo() call works (without POOM).

If I deploy the same PPC 2003 build on a WM 5.0 emulator or a real WM
5.0 device, the CeOidGetInfo call fails.

The problem, as Peter pointed out, is that Microsoft completely changed
the way POOM works in WM 5.0. In Pocket PC 2003 and earlier, all the
POOM data was stored in a property database. However, that database
isn't present at all in WM 5.0. The old POOM APIs still work, but going
directly to the database doesn't. WM 5.0 provides a new set of APIs.

That being said, Microsoft provides a new managed library,
Microsoft.WindowsMobile.PocketOutlook that provides direct managed
access to the new data.

Hope that helps,
-- John