Search parameters and unicode
Hi,
It appears in 12.02 Enterprise that it's not possible to successfully
use search parameters that include unicode characters from outside the
usual ASCII range, for example: "WHERE NAME = '?????????'"
Report builder allows that value to be used, but the search returns no
results because the SQL where clause built by Report Builder does not
prepend the 'N' to the front of the search value that is necessary to
identify it as a unicode string, e.g. "WHERE NAME = N'?????????'"
I've changed our RB source to include this, but if it's not already
included in 12.03 is it possible you could include it in the next
release (unless there's a reason not to)?
The function in question is FormatValue(const aValue: String): String;
which is a local function of
ResolveCriteria(aCriteria: TdaCriteria; aLastCriteriaType:
TdaCriteriaType; var aExpression: String): Boolean;
in daSQL.pas
Thanks,
Steve Branley
It appears in 12.02 Enterprise that it's not possible to successfully
use search parameters that include unicode characters from outside the
usual ASCII range, for example: "WHERE NAME = '?????????'"
Report builder allows that value to be used, but the search returns no
results because the SQL where clause built by Report Builder does not
prepend the 'N' to the front of the search value that is necessary to
identify it as a unicode string, e.g. "WHERE NAME = N'?????????'"
I've changed our RB source to include this, but if it's not already
included in 12.03 is it possible you could include it in the next
release (unless there's a reason not to)?
The function in question is FormatValue(const aValue: String): String;
which is a local function of
ResolveCriteria(aCriteria: TdaCriteria; aLastCriteriaType:
TdaCriteriaType; var aExpression: String): Boolean;
in daSQL.pas
Thanks,
Steve Branley
This discussion has been closed.
Comments
We can add something for the next release. What database engine are you
using? I Googled and looks like MS SQL Server has this requirement, but
perhaps other products use the same syntax. I don't think this is a SQL
standard though.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Thanks for the reply. We are indeed using MS SQL Server for which it's a
requirement. I've changed it in the Report Builder source code here, so
it's not urgent, but it's nice to not have too many custom changes to
make when updating to each new version of Report Builder. It didn't
occur to me that this would be an MS SQL specific requirement - should
haven't guessed they'd be non-standard though!