A possible approach is described here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1562812&SiteID=1

On Mar 27, 4:08 am, svnat...@gmail.com wrote:

There's no easy way to do this, however if you're willing to code,
then you could certainly achieve it.  The steps involved might be:

1.  Create the target database if needed.
2.  Open the source database.
3.  Retrieve the table schema information via the System Views (i.e.
INFORMATION_SCHEMA.COLUMNS, INFORMATION_SCHEMA.INDEXES, etc.).
4.  Build a list of Column Names for later use.
5.  Build a DDL statement to create the Table and Indexes.  You may
also need the Constraint information if any.
6.  Create the new table on the target database.
7.  Open the source table (preferably using the SqlCeResultSet for
efficiency).
8.  Open the target table (again using the SqlCeResultSet for
efficiency).
9.  Loop through each record from the source table SqlCeResultSet.
10.  Get the SqlCeUpdatableRecord for the target table SqlCeResultSet.
11.  For each column (either using the column index or based on the
list of Column Names saved), set the SqlCeUpdatableRecord value to
respective value from the source SqlCeResultSet.
12.  Perform Insert for the target SqlCeUpdatableRecord.
13.  Done.

Coding something similar to this should take few hours.  The most
difficult part will be to build the correct DDL statement to create
the target table given the variations you can have on the original
table schema.

Good luck.

- Jin

I discuss this issue in my ebook, but it does not include the newest (and
probably most appropriate approach) of using Synchronization Services. Once
the DDL is in place, syncing the tables should be fairly painless and easy
to code. VS 2008 might even do it for you by using the DataCache class.