?
Solved

sql server ntext fields only display first 255 characters

Posted on 2004-10-20
10
Medium Priority
?
294 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:mdebeer
9 Comments
 
LVL 28

Expert Comment

by:bdreed35
ID: 12363348
What type of connectivity are you using? (Native, ODBC, OLEDB).

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.
0
 
LVL 42

Expert Comment

by:frodoman
ID: 12363388
Have you tried deleting the field from your report and then adding it again (after you've verified the database)?
0
 

Author Comment

by:mdebeer
ID: 12363402
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.
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
LVL 13

Expert Comment

by:vidru
ID: 12363549
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
0
 
LVL 28

Expert Comment

by:bdreed35
ID: 12363587
How are you connecting to the database in Crystal?
0
 

Author Comment

by:mdebeer
ID: 12363860
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.
0
 

Author Comment

by:mdebeer
ID: 12363889
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?
0
 

Author Comment

by:mdebeer
ID: 12363993
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.
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 12632879
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

I hate sub reports and always consider them the last resort in any reporting solution.  The negative effect on performance and maintainability is just not worth the easy ride they give the report writer.  Nine times out of ten reporting requirements…
Hot fix for .Net Crystal Reports 10.2.3600.0 to fix problems with sub reports running on 64 bit operating systems ISSUE: Reports which contain subreports fail with error "Missing Parameter Value" DEPLOYMENT SERVER OS: Windows 2008 with 64 bi…
In this video I will demonstrate how to set up Nine, which I now consider the best alternative email app to Touchdown.
Watch the software video of Kernel Import PST to Office 365 tools which can easily import PST and OST files to Office 365 for bulk mailboxes. The process of migration is simple and user can map source and destination mailboxes and easily import data…

589 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question