On 08/17/10 10:45 PM, Lord_Devi wrote:
> Hello,
>
> Here is the catch. The SQL database itself exists at a 'home office',
> and these workers are wanting to be able to enter this data remotely; in
> an 'offline mode' as it were. Because they are required to fill out
> these forms away from the office,
in your application, when you are offline, build a batch job of the
changes they make. when the system is back online, playback this
batch, and collect any exceptions, such as collisions with other edits,
for further attention.
if the database is not too big, the clients could carry a clone from the
last time they synced.
