branch offices forms.net sql server

I was wondering if someone can tell me what Microsoft Technologies I
need to employ for the given situation:

As a small business, we keep all of our data currently in sql server
and we only have one office. We use forms.net as interfaces to the sql
server database. However, we are looking into expanding to multiple
branch offices. We are also looking into a way to expose some of the
data to the internet, so certain data can be viewed anywhere.

My question is, all of the data from all of the offices need to be
synchronized. So, how does one go about doing this? Should the database
be held in a single physical location as everyone from branch offices
all remotely update and retrieve data? If so, how do you secure this
setup ( authenticate, authorize, etc)?

What other ways is there? Can anyone point me to some strategies? I
have read about ERP systems. They store all of their data in a single
database, how does that work when people from different office
locations need to connect to data?

.

Relevant Pages

  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Word 2003/Access2000/SQLSVR
    ... SQL server being where the data is held and this is accessed through a MS ... entire database and that may be say a record for Berkshire. ... "Peter Jamieson" wrote: ... replaced with the first record on the table in use. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: MS Access DAO -> ADO.NET Migration
    ... full SQL Server and I see the logic you explained in a multi user ... allow two users to access the same database file Read/Write at any given ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MS Access DAO -> ADO.NET Migration
    ... For that it is much harder to handle the incremental identifier, ... database but although they have the data, they are not connected at the same ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... SQL Server Management Studio is nowhere to be found on my ...
    (microsoft.public.dotnet.framework.adonet)