[AccessD] Multiple Users Question - Replicated Database

Charlotte Foust cfoust at infostatsystems.com
Fri Sep 14 11:03:37 CDT 2007


The design master is synced to the other replicas, usually through an
intermediate replica, with all design changes being made to the design
master and then synced to the levels of replicas.  You don't change data
in a design master because it causes data conflicts with the replicas
that have to be hand laundered by the developer.  In replication, the
design and the data are synced separately, not simultaneously, so
changes to design to add a field and changes to data to populate that
field would result in the data being synced when the field didn't yet
exist in the replicas.  The other big reason for not working directly in
the design master (I'm not talking design changes, mind you, only data)
is that sooner or later the design master rolls over and turns up its
toes and you have to recover a replica as the new DM.  Mucking around in
the DM only increases the chance of it failing.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Michael R
Mattys
Sent: Friday, September 14, 2007 8:16 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Multiple Users Question - Replicated Database

I volunteer to be the idiot.
Why doesn't anyone ever work with the design master?

Michael R. Mattys
MapPoint & Access Dev
www.mattysconsulting.com

----- Original Message -----
From: "Julie Reardon" <prosoft6 at hotmail.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Friday, September 14, 2007 10:40 AM
Subject: Re: [AccessD] Multiple Users Question - Replicated Database


> I'm not an idiot Charlotte.  Of course, I am not working directly with
the
> design master.
>
> Julie Reardon
> PRO-SOFT of NY, Inc.
> 44 Public Square, Suite 5
> Watertown, NY  13601
> Phone:  315.785.0319
> Fax:  315.785.0323
> NYS IT Contract#CMT026A
> NYS Certified Woman-Owned Business
> www.pro-soft.net
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
> Sent: Thursday, September 13, 2007 2:12 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Multiple Users Question - Replicated Database
>
> Master copy?  You mean of the data or of the UI?  If you have a
combined
> database replicated, you're looking at trouble, not matter how you
> handle it.  I hope you don't mean the *Design Master* because nobody
> EVER works directly with that one.
>
> Charlotte Foust
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Julie
Reardon
> Sent: Thursday, September 13, 2007 10:58 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Multiple Users Question - Replicated Database
>
> Hmmmmmm.  I may have just figured it out.  I can have them create the
> inspections on the master copy on the server, where I assign a unique
> inspection id, then download those inspections to the tablet pc.  That
> way, there won't be any duplicates.
>
> Julie Reardon
> PRO-SOFT of NY, Inc.
> 44 Public Square, Suite 5
> Watertown, NY  13601
> Phone:  315.785.0319
> Fax:  315.785.0323
> NYS IT Contract#CMT026A
> NYS Certified Woman-Owned Business
> www.pro-soft.net
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Julie
Reardon
> Sent: Thursday, September 13, 2007 1:45 PM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Multiple Users Question - Replicated Database
>
> Hi,
>
> I am kind of stuck on an issue and wondered if anyone has done this.
>
> My housing inspection software is being used locally and is working
> great.
>
> However, when I wrote the software, they were only using one tablet pc
> and replicating with the master copy on the server.
>
> Now they want to send multiple inspectors out there with tablet pc's.
>
> My problem is that when they create an inspection, I assign a unique
> inspection id.  That id follows the record through the inspection
> process, and then onto the Work Order that is created when there are
> repairs needed.
>
> If I have multiple inspectors with tablet pc's, I can't create the
> unique inspection id (automatically increments by one) when the
> inspection is created on the tablet pc, because I won't know which id
> each of the tablet pc's are using until the users synch with the copy
on
> the server.
>
> Multiple inspectors means duplicate inspection id's.
>
> Is this making sense?
>
> I need a way to create a temporary inspection id that is unique and
then
> when the inspector synchs with the server, a permanent id is assigned
to
> the record.
>
> Anyone run into this?
>
> Is this the way to go about doing this?
>
> I'm not necessarily looking for code, just some opinions.
>
> Julie Reardon
> PRO-SOFT of NY, Inc.
> 44 Public Square, Suite 5
> Watertown, NY  13601
> Phone:  315.785.0319
> Fax:  315.785.0323
> NYS IT Contract#CMT026A
> NYS Certified Woman-Owned Business
> www.pro-soft.net
>
>
> --
> 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
>
> -- 
> 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 

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




More information about the AccessD mailing list