Replica Synchronisation and so on.

[Guest]

All right. I've finished my database, made a backup, and turned the original
into a Design Master. I've built a replica. The replica will be working
across our network, and i intend to make several more, however i wanted to
understand how to make it function properly before i continued. The replica
i've made is Local -- if i understand the information presented in the
helpfiles, this will allow them to edit and make changes to records, and have
them updated on the master and vice versa (unless the person using the master
happened to be editing the same record). Here's my question: How does one
automatically cause the replicas to synchronise with the master? Is this
what the options in options--advanced are for?
If there's visual basic code involved, or some outside program (i've read
about JRO, but don't quite understand its use) i'll need some help.

 

[Guest]

Replication should ONLY be used with a backend database. You should NOT use
replication on a fully contained database or frontend. This will only result
in corruption for you.

As for synchronizing, your users will either need to manually do it, or if
you have a copy of MS Replication Manager you can use it, or check here for
some automation:
http://www.utteraccess.com/forums/showthreaded.php?Cat=&Number=1422115&page=&view=&sb=5&o=


--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
__________________________________
If my post was helpful to you, please rate the post.

 

[Guest]

Perhaps i should provide some more information, so that i know i'm getting an
answer to the right question. This database does the following: imports an
excel spreadsheet, which is handmade by the person doing the importing, to
fit into the append table (currently having problems with that, too.) Each
person makes their own spreadsheet, and does their own importing. After
doing their audits, they export a new spreadsheet, which someoene else ends
up emailing elsewhere when its done. Striclty speaking, synchronising
records, keeping a copy of all of the processed data, etc, is not necessary.
How would i accomplish this?

 

[Guest]

Give each user their own copy of the database then. If the data doesn't need
to be synched between users, all they need is a separate copy of the program.
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
__________________________________
If my post was helpful to you, please rate the post.

 

[Guest]

OKay. Let us assume at a later time, that, having developed a working
utility for my group, that i wanted to change the way it worked. Lets say i
wanted just one person to import the entire spreadsheet, and allow everyone
to simply select a filter, and edit the records they needed to work on. This
would require some synchronization, though not a whole lot since they would
rarely if ever be adding or removing a record. How would this be done?

 

[George Nicholson]

What exactly needs to be synchronized?

If all users can connect to a backend file on a shared network drive, then
they can all see, filter and modify the data in that file at the same time.
This is done real-time. User A's changes can be seen by user B pretty much
immediately. Access, "as-is", can support multiple simultaneous users *as
long as the application has a proper front-end/back-end structure*.

Replication/synchronization is used when you have users that are
disconnected from the "parent" but need to modify their remote copy of the
data and update the "parent" data with their changes (and get new data from
the parent) the next time they connect to it. Nothing you have said
indicates that this is your situation, and trust me, you do not want to go
down the replication road unless it is absolutely required.