[AccessD] Replication concept

Elam, Debbie DElam at jenkens.com
Mon May 5 10:48:18 CDT 2003


I have set up the Access replication.  That has worked pretty well.  I
replicate twice a day since none of this info is more critical than that.  I
have a program that I set off with a scheduled task.  It sets off a
replication among the BEs.  In this Access program I have a table that
records the time and date after that database is successfully replicated.  I
found that much more reassuring than depending on the replication manager
that comes with the developer's edition.  I never felt I had enough records
to be absolutely sure that the replications were going exactly as I planned.
I also have a set of backup databases, one for each day of the week.  They
replicate in only on their specified day.  This really helped in recovering
from a replication error that occurred at one point.

Debbie

-----Original Message-----
From: John Colby [mailto:jcolby at colbyconsulting.com]
Sent: Monday, May 05, 2003 10:36 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Replication concept


Debbie,

How are the BEs connected, i.e. what replication mechanism?  What is the
time to replicate and how often do they replicate?

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Elam, Debbie
Sent: Monday, May 05, 2003 11:24 AM
To: 'accessd at databaseadvisors.com'
Subject: RE: [AccessD] Replication concept


I have something like this already working.  I needed a WAN solution and it
just made sense to put a BE in each city and replicate them.  Each user has
a FE on their desktop and connects to their local BE.

Debbie

-----Original Message-----
From: John Colby [mailto:jcolby at colbyconsulting.com]
Sent: Monday, May 05, 2003 10:16 AM
To: AccessD
Subject: [AccessD] Replication concept


Folks,

I just wanted to run an idea past you guys.  One of the concerns expressed
by my client's users was the time required for changes to ripple around if
we used the "standard" replication scheme of a BE on every desktop.  It
occurred to me that perhaps the client could create 2 or 3 "servers" where
each server had a copy of the BE.  Instead of 25-30 users all linked into a
single back end, have 10 users each (roughly) linked into one of three BEs.
Those three BEs then replicated amongst themselves.  The business breaks
down into three distinct sets of users (business groups) so that perhaps all
members of a group could link to the same BE, thus getting instant access to
the changes from it's group and yet still have rapid access to changes from
the other two business groups since the replication circuit would consist of
only three BEs instead of 30.

This would allow other advantages as well if the client wanted to pursue
them, such as segmented networks, with each server having it's own routers
and thus the traffic routed to each server would drop considerable.

My question to you is, does the idea of a small number of BEs (probably 3),
sitting on servers, replicating amongst themselves, linked to the FEs on
users desktop machines - does this idea make sense?

John W. Colby
www.colbyconsulting.com


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


- JENKENS & GILCHRIST E-MAIL NOTICE - This transmission may be: (1) subject
to the Attorney-Client Privilege, (2) an attorney work product, or (3)
strictly confidential. If you are not the intended recipient of this
message, you may not disclose, print, copy or disseminate this information.
If you have received this in error, please reply and notify the sender
(only) and delete the message. Unauthorized interception of this e-mail is a
violation of federal criminal law.

  This communication does not reflect an intention by the sender or the
sender's client or principal to conduct a transaction or make any agreement
by electronic means.  Nothing contained in this message or in any attachment
shall satisfy the requirements for a writing, and nothing contained herein
shall constitute a contract or electronic signature under the Electronic
Signatures in Global and National Commerce Act, any version of the Uniform
Electronic Transactions Act or any other statute governing electronic
transactions.


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


- JENKENS & GILCHRIST E-MAIL NOTICE - This transmission may be: (1) subject
to the Attorney-Client Privilege, (2) an attorney work product, or (3)
strictly confidential. If you are not the intended recipient of this
message, you may not disclose, print, copy or disseminate this information.
If you have received this in error, please reply and notify the sender
(only) and delete the message. Unauthorized interception of this e-mail is a
violation of federal criminal law.

  This communication does not reflect an intention by the sender or the
sender's client or principal to conduct a transaction or make any agreement
by electronic means.  Nothing contained in this message or in any attachment
shall satisfy the requirements for a writing, and nothing contained herein
shall constitute a contract or electronic signature under the Electronic
Signatures in Global and National Commerce Act, any version of the Uniform
Electronic Transactions Act or any other statute governing electronic
transactions.




More information about the AccessD mailing list