Is This Possible?

[Sharktyyfa]

Hi, hoping someone can help.

Access 2003, WinXP.

I have built a database that uses synchro to co-ordinate with the
mothership.

All is well.

The person i built it for wants the satellites to be able to edit the
entries in their database until it is synchro-ed(sic?) with the mothership.

At that point they should only be able to add new entries and not edit
existing records.

Is this possible?

Any and all responses welcome.
--
Sharktyyfa

[news.verizon.net]

I can't help you on replication (except to say it is not for the faint of
heart), but it would help you find a good answer if you used the precise
Access term "replication" and summarized the topic in the Subject line. Many
people best able to answer are among the busiest of participants here and
just don't have time to open posts with vague titles to see if the question
is one in their area of expertise. And, for sure, "Is This Possible?"
doesn't give much of a clue as to the content.

For other good suggestions on effective use of newsgroups, see the FAQ at
http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Access MVP
"Sharktyyfa" <sh********@sharktyyfa.com.tw> wrote in message
news:42******@clear.net.nz...

Hi, hoping someone can help.

Access 2003, WinXP.

I have built a database that uses synchro to co-ordinate with the
mothership.

All is well.

The person i built it for wants the satellites to be able to edit the
entries in their database until it is synchro-ed(sic?) with the
mothership.

At that point they should only be able to add new entries and not edit
existing records.

Is this possible?

Any and all responses welcome.
--
Sharktyyfa

[Sharktyyfa]

Okay, fair enough.

Will repost.
--
Sharktyyfa
"news.verizon.net" <bo*****@localhost.not> wrote in message
news:BMGxe.2356$Yb4.898@trnddc08...

I can't help you on replication (except to say it is not for the faint of
heart), but it would help you find a good answer if you used the precise
Access term "replication" and summarized the topic in the Subject line.
Many people best able to answer are among the busiest of participants here
and just don't have time to open posts with vague titles to see if the
question is one in their area of expertise. And, for sure, "Is This
Possible?" doesn't give much of a clue as to the content.

For other good suggestions on effective use of newsgroups, see the FAQ at
http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Access MVP
"Sharktyyfa" <sh********@sharktyyfa.com.tw> wrote in message
news:42******@clear.net.nz...

Hi, hoping someone can help.

Access 2003, WinXP.

I have built a database that uses synchro to co-ordinate with the
mothership.

All is well.

The person i built it for wants the satellites to be able to edit the
entries in their database until it is synchro-ed(sic?) with the
mothership.

At that point they should only be able to add new entries and not edit
existing records.

Is this possible?

Any and all responses welcome.
--
Sharktyyfa

[David W. Fenton]

"Sharktyyfa" <sh********@sharktyyfa.com.tw> wrote in
news:42******@clear.net.nz:

Access 2003, WinXP.

I have built a database that uses synchro to co-ordinate with the
mothership.

All is well.

The person i built it for wants the satellites to be able to edit
the entries in their database until it is synchro-ed(sic?) with
the mothership.

At that point they should only be able to add new entries and not
edit existing records.

Is this possible?

Not at the replicated table level, but you can certainly set up your
application to disable record editing in your data editing forms.
You'd have to decide exactly how to do that. One way would be to
check the connect string on the tables, and if they are connected to
the mother ship, allow editing, but if they are connected to a local
replica, disable editing in the form's OnOpen event.

Of course, that assumes that your tables are secured by some method,
and the best way, of course, is with Jet user-level security. But
that can be cracked by someone who wants to do so.

There is no reason, per se, to limit edits in a replicated app --
they will be synched. The problem, of course, is that unless you
write your own conflict resolver routines, you don't have full
control over which edits win.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc