Re: Replication ...on wireless LAN?

and I've never corrupted a database when a connection drops

it sounds to me like your jet crap is well-- crap

seriously kid

you were ranting and raving about how 'Jet Replication is 100% flawless'
and now you say that if a wirless connection is dropped then it CORRUPTS
THAT DATBASE?

David why don't you go and take a long walk off of a short pier

"lmv" <lmv@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0D7E3790-5706-4B59-A12F-B091E83790B5@xxxxxxxxxxxxxxxx
Once again... thanks for the explanation!

"David W. Fenton" wrote:

lmv <lmv@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:60E9C6C2-26E9-4221-943C-A650E94684C2@xxxxxxxxxxxxx:

Do you have to be wired or can it be wireless LAN to use Direct
Replication?

There's a difference between what you *can* do and what you *should*
do. A wireless LAN may have sufficient bandwidth to make a direct
synch feasible in terms of time, but because of the extreme
unreliability of wireless connections (which tend to constantly lose
and regain signal), it is not advisable to do a direct synch over
wireless, just as it's not advisable to attempt to use table links
connected to a back end across a wireless link.

So, if you have 2 laptops can you make a replica set wireless to
the other laptop?
And then sync? Or do you have to get into this complicated
indirect replication to do this?

You can *do* a direct synch, but it's dangerous, because a direct
synch opens the remote database across the wire. If the connection
drops while that remote database is open, you will corrupt the
remote database and likely lose replicability, which means the
remote database is no longer part of the replica set and can't be
synched. That means you'll end up having to manually recover the
data in it and then create a new replica to replace it.

I am so confused! And what if you have Office 2003
not 2000 or XP...???
The directions are so complicated it will take me a month to
figure this out!

For a one-time synch, the risk is minimal across wireless. For a
regular synch operation, I would not recommend it as it's simply too
dangerous. The time and cost of implementing indirect replication is
completely worth the effort when compared to the time and cost of
recovering from corruption/loss of replicability (and don't forget
the downtime involved during that recovery).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/



.

Relevant Pages

  • Re: Replication: Alternatives?
    ... > copy of the database. ... > cannot be connected to the LAN. ... If they can *never* be connected to the LAN, replication is ... single point of connection between the LAN and outside the LAN. ...
    (microsoft.public.access.replication)
  • Re: Almost always connected scenario
    ... You can synchronize as often as you like with merge replication. ... You don't want to use any direct-to-database connection scheme, ... Data is always saved in the local database, ... synchronization taking place every 5-10 minutes. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Replication: Alternatives?
    ... starting to familiarize myself with ?Replication?, ... different users, each with a laptop, and each with a copy of the database (or ... replication does not support the scenario where you do not have a true direct, ... indirect, or internet connection. ...
    (microsoft.public.access.replication)
  • Re: is changing design master safe?
    ... Replication is certainly one way, but you are hampered if you don't ... You *can* establish a temporary network ... connection via modem connection and RAS, however, I don't have any ... third database that you *do* copy from location to location. ...
    (microsoft.public.access.replication)
  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
Loading