Hi there,

I tried implementing a custom business logic handler in out replication
environment which consists out of a central publisher, three re-publishers
and a number of laptops as final subscribers.

In the UpdateHandler I check for updates on one table which are not
suitable at the time the replication takes place. Those changes can only
come from a subscriber. So if I detect such a change I first tried to simple
reject the change - but this makes the record persist in the state to be
rejected
at the subscriber database.

So I select the publishers record into the customDataSet and return the
value AccesspCustomDataset instead. This works fine between the central
publisher and the republishers (push subscription from publisher to
re-publisher).

When I tried to do the same at the SQL-Express databases which use a pull-
subscription to the re-publisher the record is rejected, but the custom record
is not applied at the subscriber side - the record stays in the wrong state...

I've read an article with a related problem at
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=874312&SiteID=1,
where the tip was to set the subscriber_type of the SQL-Express database
from "local" to "global" - and it worked. This shall be a bug in SQL Server...

So one question remains - will I have sideeffects when setting the
subscriber_type to "global" at the SQL Express databases ?

Regards,
Rolf