Disappearing Parameterised Filters and Filter Joins in Publication Properties page of replicatio

Hi,

We have an issue with our replication configuration when viewed through replication monitor. Parameterised Filters and joined filters don't appear in the gui. However, when we script the publication all the filters are present.

This issue only seems to occur when we have a remote distributor.

I should also point out that we have a merge push topology that uses a custom RMO synchronisation component on a separate server to either the publisher or the distributor. Also all the databases in the topology are called the same name. This has caused us other issues relating to this topology in particular so I raise it here as well although I don't expect it to be the case in this instance.

Any help would be greatly appreciated in clarifying this matter.

To get better response, can you submit this bug/issue to http://connect.microsoft.com? We can track it better there, thanks!

Disappearing Parameterised Filters and Filter Joins in Publication Properties page of replic

Hi,

We have an issue with our replication configuration when viewed through replication monitor. Parameterised Filters and joined filters don't appear in the gui. However, when we script the publication all the filters are present.

This issue only seems to occur when we have a remote distributor.

I should also point out that we have a merge push topology that uses a custom RMO synchronisation component on a separate server to either the publisher or the distributor. Also all the databases in the topology are called the same name. This has caused us other issues relating to this topology in particular so I raise it here as well although I don't expect it to be the case in this instance.

Any help would be greatly appreciated in clarifying this matter.

To get better response, can you submit this bug/issue to http://connect.microsoft.com? We can track it better there, thanks!

Disabling a publication replication schedule programatically

Is there a way that I can programatically disable a publication from
replicating if publication conflicts exists? My intent is to check is there
is publications conflicts for the pub and prevent it from replicating on its
next scheduled replication if previous conflicts exist.
You should really be trying to resolve the sources of conflict so that they
do not re-occur rather than trying to do what you propose.
With replication you want conflicts to be rare and/or trivial.
"Pete Ocasio" wrote:

> Is there a way that I can programatically disable a publication from
> replicating if publication conflicts exists? My intent is to check is there
> is publications conflicts for the pub and prevent it from replicating on its
> next scheduled replication if previous conflicts exist.
>
>
|||Thanks for your answer. I have infact tried to fix the problem. The
biggest problem is the weakest link in the chain: users. They refuse to
follow instructions even when the instructions are clear and even, written
for them. Even after they experienced a problem more than once, they
insist in repeating it. Any other ideas?
"Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
news:4CD4DEF5-6172-49A7-8265-3EA4E875CF6B@.microsoft.com...
> You should really be trying to resolve the sources of conflict so that
they[vbcol=seagreen]
> do not re-occur rather than trying to do what you propose.
> With replication you want conflicts to be rare and/or trivial.
>
> "Pete Ocasio" wrote:
there[vbcol=seagreen]
its[vbcol=seagreen]
|||See my post on your other thread - I suspect the two problems are related.