🚀 go-pugleaf

Dennis Levy / Maxine Levy wrote:
> 
> We are doing some RAD programming and have a VDB program
> presently running in 4 sites throughout the US successfully.
> We are on a mission from God to bring the program up in MS-SQL
> immediately and are attempting to bring up our program made up
> of more than 50 files and our databases (more than 60) within
> the month.
> 
> At the same time we are working with "replication" which
> includes "publishing" and "subscribing."  Does anyone have
> good experience doing this, especially with VDB. Our
> reading indicates possible stumbling blocks with the subscribing
> articles (tables) going into a 'read only' mode. Our planned
> architecture includes three layers:
> 
>       ----------------------------------------------
>                     SQL Database
>       ----------------------------------------------
>          COMPLETE DBASE DATABASE AT EACH LOCATION
>       ----------------------------------------------
>                  OUR COMPILED PROGRAM
>       ----------------------------------------------
> 

There is really very little replication can do to resolve
conflicts it two way updates automatically. You can easily
replicate in one direction but two causes problems.

Also two way updates would require versioning of fields
so you know what was changed. Lotus Notes has a lot
of functionality to handle this type of situation. For
example one place changes a persons last name and
another checks and corrects an incorrect postal/zip
code - both changes need to be replicated.

Last time I look SQL Server doesn't handle two
way replication.

Brian Evans