Stefan Hoffmann wrote in
:

After that you can dive into SQL Server Replication which is quite
easy to master, but you need some time to get into it.

The only reason to do this would be to provide disconnected access.
Keep in mind that SQL Server Express limits replication
funcationality (though not to the point that it cannot be used for
merge replication), so you might have to use a more expensive
version of SQL Server.

If you're not supporting disconnected editing for your remote users,
then you wouldn't need to do this at all.

All forms of replication are an order of magnitude more complex than
using a database without it. Conflict resolution has to be
implemented in some form (you can't ignore it without having your
data end up in a de facto corrupted state), and there are certain
schema designs that inherently do not work (for example, a self-join
with a required field is one that has to be handled very, very
carefully).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/