banalyst526
IS-IT--Management
Advice, and technical help would be much appreciated. I am a IT Analyst and know the basics of Access, but not much deeper.
Background:
We currently have a very volatile (had a code happy developer in there for awhile) Access 2000 database that the developers are doing design changes to replicas and then synchronizing to the "master" that several users synch to with their local replicas. We do a lot of updates and record additions on the local replicas. The communication between the replicas and the master is some home grown "commmgr" and not MS Jet Flow.
Should we implement two-phase commit and how do we implement it, no longer using replication since we are constantly editing and updating records? and...Shouldn't the designers be applying their changes to design after testing to the master and not a bunch of replicas, synching up the changes to the master?
Please let me know.
Thank you.
Background:
We currently have a very volatile (had a code happy developer in there for awhile) Access 2000 database that the developers are doing design changes to replicas and then synchronizing to the "master" that several users synch to with their local replicas. We do a lot of updates and record additions on the local replicas. The communication between the replicas and the master is some home grown "commmgr" and not MS Jet Flow.
Should we implement two-phase commit and how do we implement it, no longer using replication since we are constantly editing and updating records? and...Shouldn't the designers be applying their changes to design after testing to the master and not a bunch of replicas, synching up the changes to the master?
Please let me know.
Thank you.
