>This is a design advice request.
>
>We would like to implement a strategy where a local SQL Express database and a remote enterprise database are always in synch.
>
>The intention is that the the remote database is generally used, but when connections are not availabe the local client application can still switch to the local version. To make it a bit more difficult, the remote database contains data for many users, but the local database should only contain data for themselves. When connectivity is restored at the client, the databases should synch automatically. It is also possible that users will be updating the remote database from other sources such as web forms. Basically, I am looking for 2 way replication between an enterprise version of SQL and SQL express that is client based. I have come up with several rather complex ideas but I am confident that this is not such a unique scenario that a solution must be re-invented.
>
>Please advise!


Troy,

I would suggest you use
"Transactional replication" to distribute (push) all required database changes to the clients (Central server=Publisher, Local database=Subscriber) and write your own code to pull the data from the Subscribers/Local database back to the central server (creating new SQL Agent JOB on the Central server for every Subscriber/Client).

Good luck!