I appreciate your prompt response.

I ran sp_columns for ItemInventory and ItemInventoryAssembly.  The only 2 columns that can have 4095 characters are SalesDesc and PurchaseDesc, the rest of the columns are small. 

After finding the columns that could be offending I created an Access database from ItemInventory and ItemInventoryAssembly.  I sorted both of these by TimeCreated and TimeModified and searched SalesDesc and PurchaseDesc for excessive characters in recently created and modified fields.  I found that the none of the fields had excessive characters, all new fields are smaller than some of the existing ones from 9 months ago when the report was working.

Any suggestions are appreciated.

Thanks

The error started while using Enterprise Solutions V6 with the most current release, the QODBC driver was 6.00.00.155.  I updated the QODBC driver to 7.00.00.199.  Also, I have updated the Quickbooks Data to Enterprise Solutions V7 getting the same error message.  The only things that have been updated were the normal Microsoft updates and Quickbooks maintenance releases.  Also, I have moved the data file to a different computer but still receive the same error message.

The report was created with Crystal Reports VI

This was used for the InventoryValuationSummary:

sp_report InventoryValuationSummary show ItemDesc, QuantityOnHand, RowType, RowData, RowDataType parameters DateFrom = {?date_as_of}, DateTo = {?date_as_of}, ItemFilterType = 'InventoryAndAssembly'

Parameter Name = date_as_of

Prompting Text = Inventory Figures as of

Value Type = Date

Also, I have uninstalled and reinstalled the QODBC Driver.  If you need the rest of the report I would gladly upload for you.  Any help is appreciated.

Mike

A number of factors have changed since you first setup the report, so I'm going to stick with that you need to control the length of the columns being returned to your report by QODBC. An examination of the report InventoryValuationSummary shows that it's not the ItemDesc that's the cause of the problem here, but actually is the RowData and RowDataType columns which can return values as long as 4096 characters:

For this example I've extracted the first 30 characters of the RowData and RowDataType columns only:

sp_report InventoryValuationSummary show ItemDesc, QuantityOnHand, RowType, {fn LEFT("RowData", 30)} AS "Row Data", {fn LEFT("RowDataType", 30)} AS "Row Data Type"  parameters DateFrom = {?date_as_of}, DateTo = {?date_as_of}, ItemFilterType = 'InventoryAndAssembly'

Let me know if this does the trick!

I had high hopes but am still getting the error.

Any other suggestions?

Mike

I created a new report using the Crystal XI and your command, but I am still getting the error message.

I am also getting the following database warning:

More than one datasource or a stored procedure has been used in this report.  Please make sure that no SQL expression is added and no server-side group by is performed.

Any suggestions would be helpful. 

Mike 

That got rid of the Database warning, but I am still getting the error message.  I even tried to run the report using QuantityOnHand only which certainly is not a large column, but still get the error.

I have also used the rebuild data function within QB Enterprise.  It is very confusing since this report worked for so many months.

Any other suggestions are appreciated, at this point I am willing to try anything.

Thanks for your help!

Mike

Crystal Reports Professional XI Product type Full Service Pack 2

Product version 11.0.0.1994

Tom,

I certainly appreciate your effort, but is seems we are running into a wall.

Is there some other area that I should go for support on this issue?  I will need this report soon and dread manually calculating it.

Thanks

Mike