What kind of replica?

[Shiva]

Hi,

I'm trying to get familiar with the concept of replica's, but it still
confuses me a bit.
Here's my situation:

1) my database application, *.mdb file, should be distributed from time to
time to a friend of mine. His copy of the database is completely detached
from my database (no connection through shared networks, internet etc).
2) I'll keep the design master, my friend should only have replica's
3) the contents of all the tables of the replica I'll supply to him should
NOT be copied into his database. The only exception is the table Switchboard
items - so if a record is added to this table, then it should also be added
to my friend's replica.
4) Of course, the structure (=datadictionary) of tables, form's etc. should
be synchronized with the replica I'll supply to him.
5) there are several cascade deletes and referential integrity is being
enforced in the design master

How should I implement this? I was thinking of partial replica's . At first
this seemed to work, but then I suddenly got the error:

"the attempt to set a column in a partial replica violated the rule
governing partial replica's"

when I tried to delete a record in a table.
This error does NOT occur in the design master. Moreover, the error only
seems to occur in tables that are being referenced by foreign key's.

So how can I overcome this error? And is a partial replica the answer to
implement 1-5? Are there any better solutions?

Thanks a lot.

[Tom van Stiphout]

On Tue, 6 Dec 2005 23:05:33 +0100, "Shiva" <sh***@gonzo.com> wrote:

You're not using replicas what they were designed for. Since it's an
advanced topic anyway, I would advise against it.
Rather split your db in front-end (everything else, and linked tables)
and back-end (tables), and send your friend a new front-end from time
to time. The Switchboard table can remain in the front-end.

For the occasional back-end db design change, write a script to bring
the user up-to-date. Use functions like CreateField, CreateIndex, etc.

Now you're mainstream, and much more likely to survive.

-Tom.

Hi,

I'm trying to get familiar with the concept of replica's, but it still
confuses me a bit.
Here's my situation:

1) my database application, *.mdb file, should be distributed from time to
time to a friend of mine. His copy of the database is completely detached
from my database (no connection through shared networks, internet etc).
2) I'll keep the design master, my friend should only have replica's
3) the contents of all the tables of the replica I'll supply to him should
NOT be copied into his database. The only exception is the table Switchboard
items - so if a record is added to this table, then it should also be added
to my friend's replica.
4) Of course, the structure (=datadictionary) of tables, form's etc. should
be synchronized with the replica I'll supply to him.
5) there are several cascade deletes and referential integrity is being
enforced in the design master

How should I implement this? I was thinking of partial replica's . At first
this seemed to work, but then I suddenly got the error:

"the attempt to set a column in a partial replica violated the rule
governing partial replica's"

when I tried to delete a record in a table.
This error does NOT occur in the design master. Moreover, the error only
seems to occur in tables that are being referenced by foreign key's.

So how can I overcome this error? And is a partial replica the answer to
implement 1-5? Are there any better solutions?

Thanks a lot.

[Shiva]

Thanks for your reply.

You're not using replicas what they were designed for. Since it's an
advanced topic anyway, I would advise against it.
So then I wonder in what cases you'd use replicas anyway...
Rather split your db in front-end (everything else, and linked tables)
and back-end (tables), and send your friend a new front-end from time
to time. The Switchboard table can remain in the front-end.

For the occasional back-end db design change, write a script to bring
the user up-to-date. Use functions like CreateField, CreateIndex, etc.

Ok, that would be a way to do it. I'll search the Internet to find such a
script cuz my problem is such a common situation imho (and because of that
it surprise me a little that Access doesn't seem to have any standard
utilities (or VB-commands?) that resolves this problem easily).
Hopefully I'll find a script, otherwise I'll have to write it myself...

[Tom van Stiphout]

On Wed, 7 Dec 2005 09:57:54 +0100, "Shiva" <sh***@gonzo.com> wrote:

There are some articles at trigeminal.com about replication worth
reading. Bottom line: only use it for what it's designed for.

-Tom.

<clip>

So then I wonder in what cases you'd use replicas anyway... <clip>

[Shiva]

>

For the occasional back-end db design change, write a script to bring
the user up-to-date. Use functions like CreateField, CreateIndex, etc.

Now you're mainstream, and much more likely to survive.

I've downloaded and installed the utility db explorer 3.0. It's allows you
synchronize metadata (=structure of tables etc) only; it automatically
generates commands like CreateIndex after comparing 2 two different
backends. It's easy and it works!!