Forum Discussion
AlexanderM
Staff
16 years agoHi,
An update on this issue:
Looks like we have reproduce the described problem when using SQL Server 2008.
We are yet to determine whether it is related to the version of SQL Server.
We will keep you updated on the progress.