Hilary,
Thanks for the response. The situation here does not
allow users anywhere near the Subscriber. Their only
contact with the Publisher is via the front-end GUI. This
is VERY tightly controlled. That's why I'm so stumped.
Tom
[quoted text, click to view] >-----Original Message-----
>replication is reliable - your users may not be:)
>
>We have faced the same problems. The users on the
subscriber swear up and
>down they did not make changes on the subscriber, however
when you catch
>them red handed......
>"Tom" <zmptkn@yahoo.com> wrote in message
>news:225301c3731e$ddd7daf0$a601280a@phx.gbl...
>> Background:
>> 1) SQL 2K SP 3 running on Win2K Servers
>> 2) Original Snapshot Created via DTS Export from
>> Publisher to Subscriber
>> 3) Subscriber is 'primed' via script for removal of
>> certain defaults, identity columns etc.
>>
>> The problem.
>>
>> I have certain tables that have Identity-Insert OFF on
>> both the subscriber and the Publisher for Replication.
>> This is appropriate for these tables. There are
literally
>> thousands of inserts done every day that work perfectly.
>> Yet every now and then, I have an update on the
subscriber
>> that somehow has the Identity field included in the
>> insert 'Fields' list. The insert works fine on the
>> publisher, so I know the Identity field wasn't used when
>> the original transaction ran.
>>
>> How is this possible? I have financially crucial data
>> dependant on the keys and identities in these tables.
Is
>> replication reliable or not? Or am I crazy?
>>
>> Thanks,
>> Tom
>
>
>.