Replication Problem

[Terri]

I have a client with several different types of users. Most use
desktops and work off of the standard tables in a common backend from
specific frontends. The sales manager uses a laptop and needs a bunch
of tables only he and his assistant use. Most of the data on the
network he only needs to read, not change. He uses the laptop both in
the office and out.

I have his special tables set to replicate so that he and his
assistant can both use them and he can add data off line. He works on
a replica and the master is on the network so the assistant always has
access to it with linked tables. I then set up a code series that
would delete the non replicated tables and then either import or link
them depending on whether he was in the office or out.

It worked fine for about a year and a half. Now I am getting messages
about not being able to delete objects in a replica. Help!! I have got
to get this back to working properly.

Thanks,
Terri

--
Posted at author's request, using moderated http://www.dbFreaks.com interface
Thread archive: http://www.dbFreaks.com/Replication-...ict540427.html

[David W. Fenton]

Terri <no**@000.comwrote in
news:18**************************************@dbfr eaks.com:

I have his special tables set to replicate so that he and his
assistant can both use them and he can add data off line. He works
on a replica and the master is on the network so the assistant
always has access to it with linked tables. I then set up a code
series that would delete the non replicated tables and then either
import or link them depending on whether he was in the office or
out.

It worked fine for about a year and a half. Now I am getting
messages about not being able to delete objects in a replica.
Help!! I have got to get this back to working properly.

Why in the world are you deleting replicated tables? It makes no
sense. The whole point of replication is that it merges the data
changes from two users automatically.

First off, you should never have anyone editing in the Design
Master, which is a very special replica (i.e., the only one in which
you can make design changes) that should be squirrelled away
somewhere safe and never used for anything but making design changes
(you do have to synch with another replica every now and again to
keep it from expiring, but the default retention period is 1000
days, so it doesn't have to be *that* often).

Why not just give the laptop user a replica, and set up a form with
a button that allows that user to synch with the shared production
replica when connected to the office LAN? There really is no need to
be deleting tables at all. If you're doing that, then you don't
really need replication in the first place.

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