CR9 Memo Field truncated at 510 characters.

I don't think the problem is with Crystal.  CR8 and before limited strings to 255 characters but CR9 is supposed to have increased that.  I believe the max length is 64kb.

Do you have the latest service packs and hot fixes for CR9 loaded?

mlmcc

Look at

http://support.businessobjects.com/library/kbase/articles/c2013791.asp

mlmcc

I concur with mlmcc about the length of memo fields.   This could be a limitation of your ODBC driver - you may want to see if there's an updated driver available.

frodoman

Using mlmcc's link, I will verify my service pack, hot fix and ODBC driver.  I'll have to keep good notes of what I apply so I can recreate it when I reimage my machine in December.  Thank you for your direction, without it I would have believed that my formulas to limit the memo field were faulty. I'll update CR9 today and post my status.

Well, how is the best way to see the ODBC version number and the current patch/monthly update status of my software?  Any update that requires reading 48 page user guide makes me very cautious.  

ODBC versions are probably easiest seen by setting up a new odbc connection (or starting to at least) and noting the version of the appropriate dll.  Of course you can just navigate to the dll and check it's properties but using the ODBC connection on the control panel has always seemed easiest to me.

A quick google search on the particular driver or a trip to the web page for the company that distributes it should give you the latest version number.

Well, you helped me find out that I CANNOT create a new connection.  Since I had been using connections created in CR8.5, I didn't need to try until now.  The driver as listed in the Create a New Connection choice box lists ODBC (RDO) as the driver.  When I look at the file ODBCcr.dll it says that it's a Microsoft driver file version number 3.520.9030.0  

I'm connecting to a Lotus Notes (R6) database and selecting from a memo field that can be 64K.  Thank you for your very clear directions on the driver versions. My driver is Lotus NotesSQL Driver (*.nsf) Version 3.02.2003.624 File NSQL32.DLL Dated 6/24/2003.  The latest one is 3.02e dated 11/2003. I got directions from http://www.lotus.com/products/rnext.nsf/873769A79D9C5B2285256A0800720B96/3C49A37F4E4FFC5F85256C5D0069BE93?OpenDocument and will install the November 2003 version.

I've updated CR9 with critical updates and monthly patches and fixes to no avail. There is no ability to create a new connection.  I will reinstall the software today.

Well, I'm without CR9. My key code, the same one that worked in August, will not work now. I am unable to reinstall CR9.  The error message is "The Product key code "xxxxxx" is not valid or has expired."  I am hopeful that I will not need to reimage my machine.

Were you running the trial version of CR9?

mlmcc

Agree with mlmcc - sounds like you had a trial version.  If that's the case then it explains why you're having the problem - probably a bug that's been fixed, but AFAIK the patches and updates don't always fix trial versions...

frodoman

Oh no, I have the real McCoy.  I'm running version 8.5 as well and my guess is that there is some registry key or file that exists that is confusing the installation.  I will remove the upgrades and patch information in my registry and any existing folders on my machine that relate to 9.0.  There are many.

You should probably uninstall CR8.5 as well - CR doesn't always coexist well with old versions...

frodoman

Uninstalling 8.5 did not fix my error.  Will reinstall XP.

Have you had CR8 or earlier versions installed on the machine?

mlmcc

Have you ever had a trial version installed?

Ok, the problem was I used an "S" in the password vs. the number "5." I corrected the situation before needing a reimage. I only have version 9 (full version) installed.  I can create a new connection but unable to drill down within folders to find a database.  Still working on the correct install/update and drivers.

Ok, I installed the correct and updated driver, created new reports based on the Lotus Domino connection (vs. what i WAS using=the ODBC connection) and am unable to find all the fields in the tables that are shown in the connection.  In other words, it may be that i was using the incorrect driver but the new driver doesn't show all the fields that I need to see. I see the tables fine, but within that table some of fields aren't available.

Where are you missing the fields?  In the report wizard, most OLE fields (including memo) won't appear to be added to the report.  If you continue through the wizard however, you can usually add them to the report designer manually - they do appear under Report Fields in the designer.

If that's not the case then it may still be a db driver issue...

frodoman

Are the missing fields in existsing reports or when you create a new report based on a new connection?

If it is existing reports,
Open the report
Click DATABASE --> VERIFY DATABASE

mlmcc

The missing fields are in the existing report, created with the ODBC driver (yes, I still use that b/c it is so fast and easy).  However, I found one trick that is helping: before creating a new Lotus Connection, I right click on "Lotus Domino" in the connection list, choose "Options" and uncheck everything but "Tables" in the top half of the dialog box.  Doing this prior to creating a new "Lotus Domino" connection will prevent the error "NDS is running" which freezes my Notes and CR9. I will try DATABASE-->VERIFY DATABASE and then use the report designer to find the missing memo fields that are truncating with the ODBC driver.

Well, I have come to terms with the fact that I will not be able to print or view the entire memo field in CR9.