"Ricardo Alvarez" <ricardo_alvarez@nospam.iparbit.es> wrote in message
news:%23c7mpbpeGHA.3456@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> I want to know if they can help me to solve the following problem. I have
> a database duplicated by merge replication, and want to control conflicts
> that are not seen as conflicts by the replication, but they are conflicts
> with the logic of business. I explain:
>
> I have a PDA with the replicated database, and orders are added to a bill
> number. Nevertheless, in the principal database this bill has been sent,
> and more orders cannot be added. When I synchronize, it is going to be
> able to add to the bill these new orders, since the bill exists, but they
> should not be able to be added, since the bill is closed.
>
> Can I control this type of conflicts adding something to the replication?
>
> Thanks
>

> Would a stored procedure conflict resolver work for you?
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "Ricardo Alvarez" <ricardo_alvarez@nospam.iparbit.es> wrote in message
> news:%23c7mpbpeGHA.3456@TK2MSFTNGP05.phx.gbl...
>> Hi,
>>
>> I want to know if they can help me to solve the following problem. I have
>> a database duplicated by merge replication, and want to control conflicts
>> that are not seen as conflicts by the replication, but they are conflicts
>> with the logic of business. I explain:
>>
>> I have a PDA with the replicated database, and orders are added to a bill
>> number. Nevertheless, in the principal database this bill has been sent,
>> and more orders cannot be added. When I synchronize, it is going to be
>> able to add to the bill these new orders, since the bill exists, but they
>> should not be able to be added, since the bill is closed.
>>
>> Can I control this type of conflicts adding something to the replication?
>>
>> Thanks
>>
>
>

"Ricardo Alvarez" <ricardo_alvarez@nospam.iparbit.es> wrote in message
news:%23m9ZETyeGHA.1856@TK2MSFTNGP03.phx.gbl...
> Yes, I supposed that this was the correct way. But, how or from where do
> we throw these stored procedures?
>
> Thanks
>
> "Hilary Cotter" <hilary.cotter@gmail.com> escribió en el mensaje
> news:OBp1wtpeGHA.1264@TK2MSFTNGP05.phx.gbl...
>> Would a stored procedure conflict resolver work for you?
>>
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>>
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>>
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>>
>>
>> "Ricardo Alvarez" <ricardo_alvarez@nospam.iparbit.es> wrote in message
>> news:%23c7mpbpeGHA.3456@TK2MSFTNGP05.phx.gbl...
>>> Hi,
>>>
>>> I want to know if they can help me to solve the following problem. I
>>> have a database duplicated by merge replication, and want to control
>>> conflicts that are not seen as conflicts by the replication, but they
>>> are conflicts with the logic of business. I explain:
>>>
>>> I have a PDA with the replicated database, and orders are added to a
>>> bill number. Nevertheless, in the principal database this bill has been
>>> sent, and more orders cannot be added. When I synchronize, it is going
>>> to be able to add to the bill these new orders, since the bill exists,
>>> but they should not be able to be added, since the bill is closed.
>>>
>>> Can I control this type of conflicts adding something to the
>>> replication?
>>>
>>> Thanks
>>>
>>
>>
>
>