Replication is one way of handling it
http://databases.about.com/cs/sqlserver/a/aa041303a.htm
http://databases.about.com/cs/sqlserver/a/aa041303a.htm
There's a lot you can do here but it really depends. To use Replication it
takes a bit of work up front but is pretty easy after you set up your
publishers and subscribers. Books Online has a lot of info too. I don't
know if you want to expose your DB to the internet, but you could create a
Web Service that takes the local datasets, updates the DB and then refreshes
the query..this would be one other possiblity if you don't want the users
having to get connected to your network. There's a lot of possibilites but
replication is definitely a good choice here.
HTH,
Bill
--
W.G. Ryan MVP Windows - Embedded
http://forums.devbuzz.com
http://www.knowdotnet.com/dataaccess.html
http://www.msmvps.com/williamryan/
David said:
I am developing an application for use by a Company's sales force.The App.
will run on Laptops, with a Master copy of the DB on the HQ PC.There will be
number of laptop users.Basically what I want to do is - keep all of the
information on all of the Laptops + HQ in sync.Is this Replication - if so
where can I find out more about it (How exactly it works etc).If not then I
will need to dump and field changes on each laptop and send it to HQ for
updating or is there something I can do my establishing an online line....
