Re: Request Recomendation

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kos Semonski (me_at_you.com)
Date: 02/13/05 

Date: Sun, 13 Feb 2005 04:18:35 GMT

Thanks Jack. I'm going to go look for it right now. The limitations that
you have highlighted really seem to limit the heck out of replication.

I have a need that will ultimately span between 50 - 100 people. It is a
testing environment for proof of concept to later port to a Oracle server,
but I'm a bit apprehensive of letting that many people bang on a single DB
file over the intranet, thus my gravitation to replication.

If I need to personally create each replica on the machine that it will
reside, that will most certainly impact the installation time.

Can I cause a front end to initiate a back-end synchronization?

( {server DB} <-------> [replicated tables db] )<--------> [Front end]

??

Kos Semonski
Mgr. Sales Operations - Data Analysis
SBC Directory Operations

P.S. <SMILE> I do understand that Developers write code..... I'm still
studying and will become proficient in VB in the next year or so....

On Sat, 12 Feb 2005 19:01:45 -0500, Jack MacDonald wrote
(in article <dq5t011tim2lo67h5ebsr73a9k29vpm3jp@4ax.com>):

> The best sources of info that I am aware of are:
> www.trigeminal.com
> Access XX Developers Handbook (version number varies) from Sybex
>
> Some tips that I have learned:
>
> - always split your database into frontend and backend components
>
> - never replicate the frontend -- backend ONLY (tables!!)
>
> - never move a replica once it has been created unless using
> Replication manager
>
> - never attempt to use email, floppy disk, CD, USB drive, etc etc to
> move a replica from one location to another.
>
> - never use the Design Master for data entry
>
> - never include your Design Master in a scheduled synchronization.
> Always sync it manually
>
> - never sync over a WAN unless using Indirect Synchronization as
> supported by Replication Manager.
>
> - developers write code instead of macros
>
> HTH
>
>
>
> On Sat, 12 Feb 2005 12:08:38 GMT, Kos Semonski <me@you.com> wrote:
>

> **********************
> jackmacMACdonald@telusTELUS.net
> remove uppercase letters for true email
> http://www.geocities.com/jacksonmacd/ for info on MS Access security

Relevant Pages

  • Re: Split Database not allowing more than one user
    ... You're overreacting and exaggerating. ... A typical case for replication is where some of the users will be off the ... upgrade thousands of dbs at 3 Fortune 100 companies after company mergers so ... I learned many tricks from the developers of those dbs. ...
    (microsoft.public.access.security)
  • Nullreferenceexception when creating replication object
    ... merge replication for synchronization. ... Synchronization generally works OK, only sometimes I receive ... try to synchronize, ... I use SQLCE data readers on one always opened SQL CE connection a lot ...
    (microsoft.public.dotnet.framework.compactframework)
  • Nullreferenceexception when creating replicaton object
    ... merge replication for synchronization. ... Synchronization generally works OK, only sometimes I receive ... try to synchronize, ... I use SQLCE data readers on one always opened SQL CE connection a lot ...
    (microsoft.public.sqlserver.ce)
  • Re: MS ADAM/AD: Absolute simplest repl/sync solution for MS ADAM on 2 or more WinXP machines?
    ... however as ADAM has the same replication engineering as AD it ... Microsoft to talk about using the product in this way (and/or doing a lot ... > Developers of Advanced Business Collaboration Solutions for Microsoft ... >> Michael, if you won't be dissuaded from the approach you're on, why don't ...
    (microsoft.public.windows.server.active_directory)
  • Re: A good book or reference source for Replication in Access 2003
    ... > I have "Access 2000 Developers Handbook" by Litwin, ... in its coverage of replication. ... Jet replication as we know it is finished. ... if you don't have a Sharepoint ...
    (microsoft.public.access.replication)