Problem in reading unknown data character from a string field

[maulae]

Hello,
I am using Crystal 11 with SQL serve have created a ODBC based report, I am having problem in reading unknown data from a string field, my field length is 8 character long but when I pull that field in my report its says ‘Database connector Error, [ODBC Driver] character string too long (8184) [Database Vendor code 20152].
I checked in the SQL query analyzer and its shows blank in there but I don’t know what strange character causing the problem, I tried to create a formula on that field to validate that field in different ways i.e. isnull, <> ‘’, Left 7, but none of them works, I will appreciate if somebody will help to handle this field data.

 

[synapsevampire]

Since SQL Server doesn't have a "String" data type for a field, your first step should be to determine the actual SQL Server data type.

You are simply looking at what Crystal has determined it is, which is generic.

Now there are a number of ways to address this, but they're all guesswork until you supply the needed info. Remember that we need to know data types when you're speaking of data, which mean using Query Analyzer or some such, or asking your dba.

I'd try a SQL Expresion on it first, see if you can convert it to a CHAR field, such as:

CAST(table.field as varchar(254))

Something like that might work, then use the SQL Expression in lieu of the field.

As for just using Crystal, if it blows at the ODBC level, then there's little to be done bcauseou can't even get it back to Crystal.

Hopefully omething in this post will resolve.

-k

 

[maulae]

Thanks for the response, actually my report is based on tables (as my company practice) and my related database name is 'Progress' that uses the SQL syntax, and string data type is similar to varchar in SQL server. I tried to conver data type in my report through formula but it did not work, I am thinking now, there may be any field data validation check or funtion available in crystal to check and replace invalid data, or any error field before any processing, that would stop my report to hanging.
I need your expertise.
Thanks,