Re: MSDE replication experience
From: Cheval (NoSpam.Ask_at_ForEmail.com)
Date: 01/20/05
- Next message: Jonathan Parminter: "Re: Comparetive study DAO v/s JRO"
- Previous message: Jonathan Parminter: ">> Synchronize switch?"
- In reply to: Graeme Richardson: "Re: MSDE replication experience"
- Next in thread: Graham R Seach: "Re: MSDE replication experience"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 19:29:23 GMT
Most definitely! What they are doing is making a copy of the master
database. In that case you definitely should *not* have a replicated
database system at all! What they are doing is very bad. That being the
case, I would expect the following to also be true. When out in the field
and the users make changes to the data, do they come back to the office and
retype those changes in to the Master database?
Microsoft Access Replication is conceptually poles apart from what your
users understand it to be. What your users are doing is taking copies of the
Master database and only using Replication because they cannot do a Windows
Copy because the Master database in use. That's like putting diesel fuel in
an unleaded car because you couldn't get the nozzle to fit and wonder why
the car doesn't run well. 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. That's the basics.
So how to fix this?
1) Read all you can about Microsoft Access Replication.
2) Explain to the users what Replication is and how to use it.
3) Stop your users from creating replicas. Unless their replica gets
corrupt, they should only need one replica for their entire time using the
database.
4) Open the Master and go to Tools->Replication->Synchronize Now and see the
mess they have created for you. You will likely see lots of replica's
listed.
5) Update all the data so the master is up to date and Backup everything.
6) Delete the users replicas.
7) Run the Sync Now in the master to Sync each replica. (It will say that it
cannot find the replica and remove it from the replica set. (That is good.))
8) Once there is no replicas to Sync to, then create a new replica for each
user. (Their last and only replica)
9) Tell the users that from their machines (replicas) to only ever use the
Sync now to send & receive the data with the master database.
10) Smile because your done with this problem.
...
11) oh yeah, see 1) again, because there are much more harder problems that
you will encounter if you don't understand the 1) point.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
"Graeme Richardson" <graeme@wave_nospam.co.nz> wrote in message
news:csmp9a$5hg$1@lust.ihug.co.nz...
Hi Cheval, you're not reading it wrong. 90% of the time the users are
connected to the network and communicate edit master database. When they
need to go out 'in the field' they create a new replica and off they go.
Do you suspect that this is the cause of problems?
Graeme.
- Next message: Jonathan Parminter: "Re: Comparetive study DAO v/s JRO"
- Previous message: Jonathan Parminter: ">> Synchronize switch?"
- In reply to: Graeme Richardson: "Re: MSDE replication experience"
- Next in thread: Graham R Seach: "Re: MSDE replication experience"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
