>>We are in (re)design phase of an application that will be run from both handheld XP boxes that will have internet VPN connection sporadically as well as LAN desktops. SQL Server 2008 will be the LAN data store.
>>
>>The handhelds need to pull data from the LAN data store, edit/add records (including pictures/short videos), and sync that data back to the LAN data store.
>>
>>Due to the intermittant connection, I'm assuming we'll give handheld users the ability to kick off synchronization manually when they know they have a connection.
>>
>>The initial attempt of this app was done using Microsoft Sync Framework, and development dragged on and on w/o reliable synchronization until patience ran out, developer bailed, and development halted.
>>
>>So now it's handed to me to figure out how to make this thing work.
>>
>>I'm deciding whether to continue with Sync Framework (which looks cool but is so far unproven here) or jump to old style SQL merge replication (I worked with that many moons ago - certainly no walk in the park).
>>
>>Anyone have experience with Sync Framework (good or bad)?
>>
>>I'm open to suggestions.
>
>My colleague implemented Sync Framework from our .NET application. I don't think we ran into any major difficulties.

I think I'm going to play with that tomorrow and see if I can make sense of it. From what I read, it sounds like it should be workable. I haven't seen a good, complete, how-to on it yet though.