"Paul Devenney" <paul@spamgohere.com> wrote in message
news:eIgIkKeSHHA.4028@TK2MSFTNGP04.phx.gbl...
> *bump*
>
>
> "Microsoft News Groups" <paul@spamgohere.com> wrote in message
> news:eEasPpUSHHA.4404@TK2MSFTNGP03.phx.gbl...
>> Hi All,
>>
>> I am using a merge pull replication with the problem shown in the
>> scenario below:
>>
>> 1) Organisation 'A' is added to tblOrganisations on the "server"
>> 2) "user" synchronises and does not add these organisations because the
>> filter restricts the subscription to only those oganisations that are
>> clients from a linking table
>> 3) server database updated to add organisation 'A' to the users list of
>> clients
>> 4) client synchronises again and finds the following:
>> the new row from the linking table has been synchronised
>> the organisation referred to in the linking table has NOT been
>> synchronised.
>>
>>
>> I now understand that this is because the merge handler believes (rightly
>> I guess) that there have been no changes to the Organisations table since
>> the last download. However the filter conversely indicates that there is
>> new information
>>
>> SELECT <published_columns> FROM [dbo].[tblOrganisations] WHERE
>> convert(nchar, OrganisationID) = HOST_NAME() OR OrganisationID IN
>>
>> (
>>
>> SELECT ClientID
>>
>> FROM tblProviderClients_tempR1
>>
>> WHERE convert(nchar, ProviderID) = HOST_NAME()
>>
>> )
>>
>> I can prove my case by changing the detail of any field in Organisation
>> A - the next time replication occurs it makes the correct decision based
>> on the filter.
>>
>>
>> If this is "acting as intended" then how should I ensure that changes
>> affecting the filter criteria when no other data has changed actually
>> merges the data I need? I'm guessing this is fairly newbie....
>>
>> cheers,
>>
>> Paul
>>
>
>

"Microsoft News Groups" <paul@spamgohere.com> wrote in message
news:eEasPpUSHHA.4404@TK2MSFTNGP03.phx.gbl...
> Hi All,
>
> I am using a merge pull replication with the problem shown in the scenario
> below:
>
> 1) Organisation 'A' is added to tblOrganisations on the "server"
> 2) "user" synchronises and does not add these organisations because the
> filter restricts the subscription to only those oganisations that are
> clients from a linking table
> 3) server database updated to add organisation 'A' to the users list of
> clients
> 4) client synchronises again and finds the following:
> the new row from the linking table has been synchronised
> the organisation referred to in the linking table has NOT been
> synchronised.
>
>
> I now understand that this is because the merge handler believes (rightly
> I guess) that there have been no changes to the Organisations table since
> the last download. However the filter conversely indicates that there is
> new information
>
> SELECT <published_columns> FROM [dbo].[tblOrganisations] WHERE
> convert(nchar, OrganisationID) = HOST_NAME() OR OrganisationID IN
>
> (
>
> SELECT ClientID
>
> FROM tblProviderClients_tempR1
>
> WHERE convert(nchar, ProviderID) = HOST_NAME()
>
> )
>
> I can prove my case by changing the detail of any field in Organisation
> A - the next time replication occurs it makes the correct decision based
> on the filter.
>
>
> If this is "acting as intended" then how should I ensure that changes
> affecting the filter criteria when no other data has changed actually
> merges the data I need? I'm guessing this is fairly newbie....
>
> cheers,
>
> Paul
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:%23VrNJogSHHA.3592@TK2MSFTNGP03.phx.gbl...
>I think what you need to do is implement a join filter. It is unclear to
>me from what you have described that you are not using join filters.
>
>
> --
> Hilary Cotter
>
> 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
>
>
>
> "Paul Devenney" <paul@spamgohere.com> wrote in message
> news:eIgIkKeSHHA.4028@TK2MSFTNGP04.phx.gbl...
>> *bump*
>>
>>
>> "Microsoft News Groups" <paul@spamgohere.com> wrote in message
>> news:eEasPpUSHHA.4404@TK2MSFTNGP03.phx.gbl...
>>> Hi All,
>>>
>>> I am using a merge pull replication with the problem shown in the
>>> scenario below:
>>>
>>> 1) Organisation 'A' is added to tblOrganisations on the "server"
>>> 2) "user" synchronises and does not add these organisations because the
>>> filter restricts the subscription to only those oganisations that are
>>> clients from a linking table
>>> 3) server database updated to add organisation 'A' to the users list of
>>> clients
>>> 4) client synchronises again and finds the following:
>>> the new row from the linking table has been synchronised
>>> the organisation referred to in the linking table has NOT
>>> been synchronised.
>>>
>>>
>>> I now understand that this is because the merge handler believes
>>> (rightly I guess) that there have been no changes to the Organisations
>>> table since the last download. However the filter conversely indicates
>>> that there is new information
>>>
>>> SELECT <published_columns> FROM [dbo].[tblOrganisations] WHERE
>>> convert(nchar, OrganisationID) = HOST_NAME() OR OrganisationID IN
>>>
>>> (
>>>
>>> SELECT ClientID
>>>
>>> FROM tblProviderClients_tempR1
>>>
>>> WHERE convert(nchar, ProviderID) = HOST_NAME()
>>>
>>> )
>>>
>>> I can prove my case by changing the detail of any field in Organisation
>>> A - the next time replication occurs it makes the correct decision based
>>> on the filter.
>>>
>>>
>>> If this is "acting as intended" then how should I ensure that changes
>>> affecting the filter criteria when no other data has changed actually
>>> merges the data I need? I'm guessing this is fairly newbie....
>>>
>>> cheers,
>>>
>>> Paul
>>>
>>
>>
>
>