Issues Using SQL CE 3.5 With MapPoint 2006?

Has anyone else had difficulties using SQL CE with MapPoint 2006?
I had assumed that since they both 'talked' OLEDB, they should be compatible with one another.

I have approx 15,000 rows in a SQL CE Table with Lat and Long columns that I'd like to import or link with MapPoint.

I've created a .udl file with the OLEDB connection string and sdf filename like so:

[oledb]
; Everything after this line is an OLE DB initstring
Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data Source=c: estsqlcompactdb estdata.sdf;

Which I can select from the MapPoint Import/Link wizard and it lets me choose a table to import.
It shows a preview of the data in the table, lets me choose column mappings, and if I'm attempting to link data it asks me to choose a column to use as the primary key.

If I attempt to import data it essentially spins forever importing row

'15588 of -1 records mapped; 0 not mapped', (ie. it cycles through all the rows that exist in the table but never completes, then only thing I can do is press 'Cancel') and if I attempt to link data I just get an error message. "Failed to link data"
My workaround for this behaviour is potentially to write small process using System.Data.SqlServerCe or ADO to import the data into MapPoint by calling the MapPoint DataSet APIs directly, but I think you ought to be able to link the data right in using the udl datalink method.