CR 9, ODBC, String [4096] limitation

[skipsubs]

I'm using CR9 to report from an ODBC datasource with a field that contains 10,000+ ASCII characters in some rows. When I map this into CR, it shows as String [4096]. Sure enough, data after 4096 characters is truncated in the report. I'm hoping someone knows how to get around this serious limitation. Any help will be appreciated.

Skip

 

[synapsevampire]

Well, you need to post the database type.

You may be able to use SQL Expressions (these are performed on the database) to parse the data out into several fields, such as:

substring(table.field,1,4000)

substring(table.field,4001,8000)

substring(table.field,8001,12000)

etc.

When asking about databases, please understand that the best solutions are pushing the processing back to the database, so post your database type, and it's great that you posted that you have ODBC connectivity.

-k

 

[skipsubs]

Thanks for the response. The database is Intersystems Cache 5.0. Yes, I suppose I could use SQL to break up the string, but that leads me to another question. I would have to put it back together in a formula. Do formula's have a string length limitation?

 

[synapsevampire]

You don't need to put it back together in a formula, drop them into a text object.

-k

 

[skipsubs]

I found a problem with text objects earlier, they do not format CRLF properly. A database field DOES format embedded CRLF's, and I'm assuming that a formula would also.