Direct Synchronizing local replica with Hub replica
- From: "mattb" <matthew.burke@xxxxxxxxxxxxx>
- Date: 1 May 2006 11:35:57 -0700
Here's where I'm at (thanks to replies found in this group):
1.Split database into front end and back end (*_be.mdb) files.
2.Moved existing back end into a protected folder that will not be
accessible to casual users.
3.Opened the back end and created a replica.
5.Put the replica back in the folder where the back end was before
(i.e. where database was split - this will now be the production
replica).
6.Copied the "production" replica over to the laptop into its final
location on the laptop.
7.Copied the front end to the laptop and re-linked it to the tables
local to the replica on the laptop.
Now the problem is when I try to synchronize the local back-end with
the "production" replica, it wants to look at the Design Master. My
understanding is that this is NOT what I want to do. In the
synchronization window I can select the drop down window and select the
"production" replica, but the next time I want to synchronize my local
back-end with the "production" back-end the same thing happens. This
will "work", but would be far too complicated for the average user.
Asking them to even do their own synchronization is probably pushing
it.
Shouldn't this synchronization setting in Access stay put?
(i.e. Tools/Replication/Synchronize Now)
Thank you,
Matthew
.
- Follow-Ups:
- Re: Direct Synchronizing local replica with Hub replica
- From: David W. Fenton
- Re: Direct Synchronizing local replica with Hub replica
- Next by Date: Re: Direct Synchronizing local replica with Hub replica
- Next by thread: Re: Direct Synchronizing local replica with Hub replica
- Index(es):
Relevant Pages
|
