Architecture Walkthrough

Hello,

I'm developing my first real CF application for PocketPC, and I'd like
to start a dialog about the architecture I should use based on my
requirements. I have read through the MSDN materials, but they all
seem focused on the device directly accessing the Server in a variety
of ways. This does not fit my requirements, so I'm seeking other
options.

The basic flow is:
1) .NET PC program prepares data from a database.
2) Data is transferred to the device.
3) Device is carried to the field, where the data is updated.
4) Device is brought back to the home computer and data is trasnferred
back to the PC.
5) PC program allows the user to review/edit data prior to updating the
database.

The PC loads the data into a DataSet, so I know I can use the
DataSet.WriteXML() method to create an XML file to transfer the data,
but I have some questions:
1) Transfer where and how?
2) Is there a way through the file system to guarantee I'll always find
the right path on the Device?
3) Can I even access the devices file structure theough my program?
4) Do I need to serialize the file, or is straight XML text sufficient?

Once I have the XML file on the device, what should I do with it? I
figure I have two options:

1) Use ReadXML() to populate my runtime application. The size of my
data should be fairly small, so this won't really be a problem, but
won't I need to re-create the XML file every time the user makes a
change? Also, according to the docs, relative paths are not allowed in
the CF. It seems I need a "Pathing Primer" for mobile devices.

2) Use SQL Server 2000 CE. I have found some information about this,
and I'm pretty comfortable with ADO.NET, so this is an attractive
option, but I can't seem to find any solid information about licensing,
installation, distribution, etc. I'm going to have to come to grips
with this eventually, so if anyone has any good links or tutorials,
that would be appreciated.

I guess my biggest frustration is that all the examples I can find of
mobile development center on Synchronization directly with servers, and
that's not what this project requires. Any discussion or comments are
welcome.

Thanks,

Joel