Re: Setup auto sync/replication

David, thank you...

All users imputing data into database daily, The data entered in on the
laptops is in a seperate table than the data entered on the 4 workstations.

The chances of changing same fields is possible but not likely.

design and form changes maybe a couple of times a year.

Yes, I do have some in the office capable of handling conflicts.

Is the code I copied here what i am looking for?
Public Sub SynchReplica(dbSource As DAO.Database, _
strDestinationMDB As String, _
Optional StrDescription As String = "Replica")
Dim strMsg As String

If Len(Dir(strDestinationDB)) <> 0 Then
If Len(Dir(strDestinationMDB)) = 0 Then
'create replica
dbSource.MakeReplica strDestinationMDB, StrDescription
Else
'synch with replica
dbSource.Synchronize strDestinationMDB
End If
Else
strMsg = "Could not connect to " & strDestinationDB
strMsg = strMsg & vbCrLf & " " & vbCrLf
strMsg = strMsg & "You may not be connected to the network."
MsgBox strMsg, vbExclamation, "Could not find replica!"
End If
End Sub


Can I make a copy for the Replica and put in on each machine or must I
create a seperate replica for each machine?

Should I be considering...
With the 4 workstations in the office, Should I split the database as
opposed to replication?

and the 6 laptops replicate the Backend only.??

Tonkle


"David W. Fenton" wrote:

> =?Utf-8?B?VG9ua2xl?= <Tonkle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> news:1A06A79A-4974-461C-A408-08442F1FCCA2@xxxxxxxxxxxxx:
>
> > I have a client running an access database, I am setting up
> > replication of the database. They would like to have clients in
> > the field with laptops to be able to make data changes and when
> > they return to the office upon logging on to the network they
> > could have their changes auto sync.?
> >
> > Also, to create an "one button" script or program that would allow
> > manual sync to simplify steps for staff.
> >
> > Syncing would be bi-directional as to update new clients added to
> > laptops.
> >
> > Can this be done?
> >
> > Basic setup - Server 2003 holding master database
> > 4 workstations in office adding data and new clients throughout
> > the day 6 laptops updating data only in the field
>
> Yes, of course it can be done.
>
> The code to do the synchronization is remarkably simple, and I've
> posted variations of it in this newsgroup multiple times.
>
> The hard part is the resolution of conflicts. First, you have to see
> if there are any, then you have to have somebody very smart resolve
> them using the built-in conflict resolver, or build your own.
>
> The former is subject to human error.
>
> The latter requires a lot of skill as a programmer, and is not
> trivial.
>
> However, if your app is designed properly and truly suitable for
> replication, there oughtn't be many conflicts in the first place, so
> there should only seldom be an actual conflict to resolve. However,
> you need to have the code that synchs check to see if it's created
> any conflicts, and if so, tell the user what they have to do to fix
> the problem. I think it's best to refer this to an administrator --
> i.e., a single intelligent person in the home office who should
> understand the data well enough to be able to resolve the conflicts.
>
> --
> David W. Fenton http://www.bway.net/~dfenton
> dfenton at bway dot net http://www.bway.net/~dfassoc
>
.