Debtors Invoice

[Steve Hutchins]

Hi Mike,

Yep all good the stored procedure worked so it's an issue changing (updating) the stored procedure used on the Crystal Report - I've used the standard invoice that comes with Jiwa with no modifications.

Steve

[Mike.Sheen]

Hi Mike,

Yep all good the stored procedure worked so it's an issue changing (updating) the stored procedure used on the Crystal Report - I've used the standard invoice that comes with Jiwa with no modifications.

Steve

Hi Steve,

What version of Jiwa are you testing with?

[Steve Hutchins]

We're running 157 but I'm not getting that far the error occurs when trying to update the stored procedure from the standard to the modified one in Crystal....

[Mike.Sheen]

We're running 157 but I'm not getting that far the error occurs when trying to update the stored procedure from the standard to the modified one in Crystal....

Right - I have found the problem.

When you supply the stored procedure a blank or invalid InvoiceHistoryID, it will give the error, but not when you supply a valid InvoiceHistoryID. That explains why it works when run in Management Studio, but not Crystal Reports.

This is due to another fault in the stored procedure - a special case where no lines were returned for the provided InvoiceHistoryID, a dummy row is constructed and that was missing the DebtorPartNo column.

I was using "Visual Studio with Crystal Reports for Visual Studio, Developer Edition SP 13" and from your screenshot It looks like you were using Crystal Reports - which does behave differently - so that may explain why when I set the datasource of the report to the stored procedure it worked, but not for you.

Attached is another revised version of the stored proc which should address the issue (finally).