Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
A custom SQL Server business logic handler replaces an empty string with an end-of-string character
Article ID: 2598605 - View products that this article applies to.
Consider the following scenario:
This issue occurs because of how the merge agent components and the business logic handler pass data in and out of the intermediate variables.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
You may be able to work around this issue by using the nvarchar data type instead of the varchar data type.
The problem that is described in the "Symptoms" section can occur if the custom business logic handler handles conflicting UPDATE statements at the publisher and subscriber. The empty string is replaced by the single end-of-string character after the publisher or subscriber dataset is copied into the custom dataset, and the custom dataset is then passed to the merge replication reconciler.
Additionally, this issue occurs if the data is not changed in custom code that resembles the following:
Article ID: 2598605 - Last Review: May 22, 2012 - Revision: 2.0