Sigurd-
If the Master is not corrupted, then rebuild two copies from it and give them to
the two users should be the first step. You can sort out the rest later.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
<http://www.viescas.com/> http://www.viescas.com/
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Sigurd Andersen
Sent: Sunday, May 27, 2012 11:52 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Repair on DB open?
I've only had preliminary conversations with the new client,
but my understanding is that there's a "replication master"
in Canada which is used to coordinate changes to either of
the two "live" copies of the database.
The two users are in different countries, the replicating is done
overnight. I don't know what sort of cross-location connectivity
they have.
I'll look at the link you suggest for alternatives.
Thanks for your quick reply.
Sigurd
On 5/27/2012 12:47 PM, John Viescas wrote:
>
> Sigurd-
>
> Replication has been "deprecated" -- that means MSFT gave up
> supporting it. It's
> full of bugs, and isn't recommended at all.
>
> Which user has the "master" database? The "master" should be on a
> share that
> both people can get to, and they should "sync" with the master, not
> each other.
>
> Is there any other way you can "sync" the data? If not, you can find
> lots of
> tips here:
>
> http://www.trigeminal.com/usenet/usenet.asp?1033
>
> .. including a utility to help you "un-replicate" the databases.
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
> ----------------------------------
>
> From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
> <mailto:MS_Access_Professionals%40yahoogroups.com>
> [mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
> <mailto:MS_Access_Professionals%40yahoogroups.com>] On Behalf Of
> Sigurd Andersen
> Sent: Sunday, May 27, 2012 5:56 PM
> To: ms_access_professionals@yahoogroups.com
<mailto:ms_access_professionals%40yahoogroups.com>
> <mailto:ms_access_professionals%40yahoogroups.com>
> Subject: [MS_AccessPros] Repair on DB open?
>
>
> I've just started working with a new client. They have a database
> created by self-taught users. It's been in use for many years. It's used
> by one person in the US, and one person in Canada. Each has a
> stand-alone copy of the database (no split into front end & back end).
> They use replication on a regular schedule to keep the two copies
> synchronized.
> Every time the database is opened, it automatically goes through some
> sort of "Repair". This happens when I open a copy of the database on my
> computer, too. I made a copy of the database by opening a blank database
> and importing all tables, queries, etc. to it. When I open this copy,
> there is no "Repair."
>
> Any thoughts as to why there's a "Repair" every time the DB is opened? I
> haven't worked with replicated DB's before - is it something to do with
> this? (Any pointers to a good overview of replication or alternatives
> for synchronizing two DB's at distant locations?)
>
> Thanks in advance
> Sigurd Andersen
>
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar