Understanding replication!

[hog]

Hi, totally new to this concept?

I intend to have a front end application on users desktops, the replica, and the master copy on our server.

Do I understand it right that if a user opens their copy I could have it coded that it syncs with the master?

I have looked at the help in Access2002 and for the sync method it says it deletes the replica first? How would this work if the user has it open?

My book states these lines;

rep.activeconection = "path to sourcer eplica"

rep.synchronize "path to target replica", exchangetype, jrsyncmodedirect

First I get an error on first line saying oject not set? The help states a connection object but the book does not?

is the source the replica or the master?

any snippets would be greatfully received

thnx

 

[hog]

just found this code on this site;

Dim repMaster As New JRO.Replica
repMaster.ActiveConnection = currentproject.connection
repMaster.Synchronize “C:\Path to replica”, jrSyncTypeImpExp, jrSyncModeDirect

but does this not mean this runs from the master?

I want the replica to check with the master on each startup to sync itself with the master?

 

[hog]

OK I seem to be able to get this to work now...only taken me all morning but now I find another problem!

No forms, linked tables queries etc replicate across??

I found this on this site dated june 2002, is this still the case?

-----
In theory they can be replicated. However, in practice replication applied to DB objects others than TableDefs and the data inside is a far too unreliable and heavy process (especially when involving forms, reports and modules).

MS itslef ackowledges that fact in its white paper on replication (a must read) and recommends the classical approach:
Split your DB FE/BE (BE with only tableDefs and data, FE with everything else plus eventually a few tables that should not be replicated)
Replicate only your BE
------