"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:efJCeonXEHA.1144@TK2MSFTNGP10.phx.gbl...
> The problem is that if the row was deleted at the publisher, there
wouldn't
> be a conflict - a conflict implies concurrent updates.
> If the row was deleted at the publisher, ideally what would you want to
> occur? Normally a delete is replicated as a delete, regardless of the
> conflict resolution mechanism chosen.
> HTH,
> Paul Ibison
>
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:efJCeonXEHA.1144@TK2MSFTNGP10.phx.gbl...
> The problem is that if the row was deleted at the publisher, there
wouldn't
> be a conflict - a conflict implies concurrent updates.
> If the row was deleted at the publisher, ideally what would you want to
> occur? Normally a delete is replicated as a delete, regardless of the
> conflict resolution mechanism chosen.
> HTH,
> Paul Ibison
>
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:uqhIJkrXEHA.2408@tk2msftngp13.phx.gbl...
> Is this error message received from the custom resolver?
> My understanding is that SQL Server stored procedure resolvers will be
> invoked only to handle update conflicts.
> Regards,
> Paul Ibison
>
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:uaVDnqtXEHA.2816@TK2MSFTNGP11.phx.gbl...
> OK, then if you want a resolver (custom) that deals with both deletes and
> updates then have a look at the C++ sample. I haven't used it but I'm
pretty
> sure that the custom stored procedure resolver only applies to update
> conflicts.
> HTH,
> Paul Ibison
>
>

>-----Original Message-----
>I wrote a stored procedure that works. I tested it with
two 2K servers, now
>I need to test with SQL CE.
>
>Thanks for your help.
>
>Here is my code.
>
>-- this resolver forces subscriber to win but allows
deletes to have
>precidence over updates
>--
>-- NB: the 'Microsoft SQL Server Subscriber Always Wins
Conflict Resolver'
>lets updates
>-- to the subscriber to win over deletes on the publisher
>
>CREATE PROC sp_sub_wins_resolver
>@tableowner sysname,
>@tablename sysname,
>@rowguid uniqueidentifier,
>@subscriber sysname,
>@subscriber_db sysname,
>@log_conflict int OUTPUT,
>@conflict_message nvarchar(512) OUTPUT
>AS
>DECLARE
>@sub_qualified_name NVARCHAR(392),
>@select_string NVARCHAR(2000)
>
>-- generate query that will return the conflicting
subscriber row
>SELECT
>@sub_qualified_name=QUOTENAME(@subscriber)+'.'+QUOTENAME
(@subscriber_db)+'.'
>+QUOTENAME('dbo')+'.'+QUOTENAME(@tablename)
>SELECT @select_string='SELECT * FROM ' +
@sub_qualified_name + ' WHERE
>rowguid = ''' + convert(nchar(36),@rowguid) + ''''
>
>-- return row from subscriber as winner
>exec sp_executesql @select_string
>
>-- log publisher lost conflict
>RETURN(2)
>GO
>
>
>
>
>"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in
message
>news:uaVDnqtXEHA.2816@TK2MSFTNGP11.phx.gbl...
>> OK, then if you want a resolver (custom) that deals
with both deletes and
>> updates then have a look at the C++ sample. I haven't
used it but I'm
>pretty
>> sure that the custom stored procedure resolver only
applies to update
>> conflicts.
>> HTH,
>> Paul Ibison
>>
>>
>
>
>.