mdebeer
asked on
sql server ntext fields only display first 255 characters
I have a report built with CR 9.0 that has multiple ntext fields. The fields that were originally defined as ntext show in their entirety. The fields that were originally varchar and were later converted to ntext only show the first 255 characters. I've tried verifying the database and pointing to another datasource with no luck. If I run a query in Query Analyzer, Access, etc. I get all the text returned.
Have you tried deleting the field from your report and then adding it again (after you've verified the database)?
ASKER
Yes, I tried that and also tried creating a new report that points to a copy of the database and I get just 255 chars from that too.
It could be that it just doesn't like NTEXT fields. Any chance you can create a View of the table that converts the NTEXT field to TEXT as a test?
-dave
-dave
How are you connecting to the database in Crystal?
ASKER
I converted the field from NTEXT to TEXT and got the same result. I am connecting to the database in Crystal using the OLE DB driver for SQL Server then pointing to an IP address and then pointing to a view.
ASKER
Here's some more information. The field was originally varchar(300) and I converted it to ntext (and just now to text). When I go to the properties for the field in CR it shows the length as still being 300 characters (I guessed it was 255 but apparently it's 300). Anyway, CR is still using the old definition of the field even thought I've connected to other databases, done verify database, etc. Any ideas?
ASKER
I think I've figured out a solution. I removed the field from my view, then ran verify database. Then added it back, then ran verify database again and it showed all the text. CR does some great stuff but it sure is buggy. Seems like I'm always doing goofy workarounds like this to solve problems. Anyway, thanks to everyone for you input.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have always had good resutls with ODBC, so you can try that. I avoid the Native SQL Server driver that comes with Crystal since it has not been updated in a long time.