david w fenton

Why would they do that when they could connect to the actual hub
replica that in your scenario everyone is synching with? I don't see
how you got such a weird idea!

Well, I haven't ever owned any MOD version of Office, so I can't
say.

What I do know is that the Access UI includes a conflict resolver.
Michael Kaplan wrote it, in fact. And it must of necessity be a part
of the Access UI, since the Access UI allows you to create and
synchronize replicas.

I've already addressed conflict resolution in several of my replies.
What's missing from my replies (i.e., what still doesn't make sense)?


Replication Manager used to come as a part of the developer tools. I
don't know where it is included nowadays.

Once you buy a copy of the MOD, you have a license to distribute it
to your clients.


I'm not sure where your basic idea went wrong and how you got so far
off track.

I also have the same puzzlement for people who don't split
databases. The Access documentation since at least version 2 has
always recommended splitting for any multi-user database, and the
first multi-user application I ever created was split (it was my
second Access app ever).

In the case of replication topology, it's all so basic to me that I
don't know where or how I learned the basics. Most of it was
learning by doing, reading documentation, MichKa's website and this
newsgroup.

But I've been at it since 1997, and did most of my complex
replication projects in 1998-99. Since then I've done not much with
replication, and nothing that's very complicated.

I was reading the newsgroup archives to see what MichKa's comments
on JRO were, and I ran across an article by someone else that
described the process of what you want to do this way:

The proper replication concept is that each user is given 1
replica by the database administrator/creator. The user then
adds, edits and deletes data in their replica only. They then
synchronize that replica with the design master to send their
changes to the master and receive the masters changes.


...[when the user returns to the office, she would] synchronize
the replica to the hub...then relink the front end to the hub.
Then when the user leaves the office, they synchronize
again...then relink the front end to their local replica.

I'd advised you on this in an earlier post, but in a rather wordy
fasthion, and not so simply and straightforwardly.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc