Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why CR limits text field up to 255 symbols?

Status
Not open for further replies.

Bartes

Programmer
Jun 9, 2001
3
0
0
RU
I have Db with text field that contains more than 255 symbols, and it's impossible to make good report with that fields, because CR limits it up to 255 symbols. Is there any possible solutions how I can show that fields in my report?
 
What is your database? Why do you need fields longer than 254 characters?
You have a variety of options, but they depend on the database type and what you are trying to achieve by using these large fields. Malcolm Wynden
I'm for sale at malcolm@wynden.net
 
My Database is MS Exchange and I would like to export "Description" field from this DB, but this field may be longer than 254 symbols. I've choosed EXCHANGE driver to export all fields from DB. Should I use another driver or change options in CR report?

Thanks in advance.
 
If you just want to print the Description on the report, then you can show that field in the report. The only restriction is that you cannot use the Description field in a formula field, other than to check to see if it is null. Malcolm Wynden
Authorized Crystal Engineer
malcolm@wynden.net
 
I'm having the same problem as that mentioned above: I have 2 fields from a SQL Server 7.0 database that are varchar(2000) and varchar(5800), and in Crystal 7.0 these are displayed as type string and length 255 (when you right click on the field in Crystal and click 'browse field data' you see this) and I don't see anywhere to change this length so the whole field can be on the report.

Thanks for any input,
Ray
 
Stop trying guys, I've lost a lot of time on this issue myself and the only solution is - as far as I know - to upgrade to version 8.5

:(

CR sucks

TheBazZ
 
I would hope there would be a way to get Crystal 7.0 to treat these fields as memo instead of string. This is what it does for Access Database fields that are this large, but once I switched the database to SQL Server it started considering them string instead of memo....
 
In case anyone is having this problem, an answer that ended up working for me is to Convert the database driver to an ODBC driver, using a machine dsn (you need to create the dsn first and then in Crystal go to Database > Convert Database Driver, pick ODBC and then pick your driver from the list). Now the whole field is showing up even over 255 characters!!!
 
>the only solution is - as far as I know - to
>upgrade to version 8.5

How does version 8.5 help? Does it use longer than 254 chars?
 
Memo fields are treated the same by both 7, 8, 8.5 (possibly v5 and 6 as well)
all fields over 254 chars are converted to memo fields which can be displayed within the reports, they just cannot be used in formulas. If your not seeing the fields displayed at all, it could be a variety of issues, either field definitions, or db drivers being used. Do you know if you are using a MR1 version of crystal 7? You might want to check the crystal main site and make sure you have the latest drivers.
Hope this helps!
-Bruce Seagate Certified RCAD Specialist.
-Bruce Thuel-Chassaigne
roadkill150@hotmail.com
 
I have also read that the SQL Server native driver does truncate VarChars to 255, but that that ODBC driver for SQL Server will show the full field as a memo. I am not sure if there is a similar pattern for MS Exchange. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB
tek@kenhamady.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top