CR8.5 crashes after dbase changes

[WarrenTheWindmill]

I am having major problems with 4 reports written recently for a client. We have made some changes to the database and the reports now crash when I attempt to run with a CRW32.exe error.

I have referred to the Crystal Knowledge Base article number c2004374 on the subject which says either:

fields exist in the report that no longer exist in the database (I checked and there aren't any)

filed names have been changed in the database (Checked and also ok)

I have also checked and rechecked all the basic stuff like sub report links and the {table.field} = {?PM-param name} conversion to {table.field} in {?PM-param name} issue in subreports

Worringly there is a thrd option which says: "If the issue does not lie within record selection....etc etc....If the report does not refresh, the issue lies elsewhere, and extends beyond the limits of this document"

Having commented out record selection I can now get the report to refresh without crashing, but the subreports (of which there are 2) don't return any data. All I get is the Report title, which is basically all there is in the main report.

Has anyone any experience of this problem or anything similar? Please note this is not directly linked to the problem I posted yesterday.

That one is similar (but in newly developed report) in that I cannot get the subreports to return data even though if I run them stand alone they do.

I am questioning:

My own ability!
Crystal Reports as a viable reporting tool for real world solutions that extend beyond the most simple. I have been using Crystal since V6 and seem to have regularly struggled with what have turned out to be software bugs.

If anyone has anything to offer that might help I would be very grateful.

A last resort is Crystal themselves, however previous experience does not fill me with confidence.

 

[kenhamady]

Have you tried verifying the database in both main and subreports? That will identify any changes that Crystal thinks are there.

What was the selection formula that you commented out?
(Post it here) Ken Hamady

http://www.kenhamady.com/

On-site custom Crystal Reports Training and Consulting.
Quick Reference Guide to using Crystal in VB.

 

[WarrenTheWindmill]

Hi Ken
Thanks for your response. I had verified the database. I have now discovered the cause of the problem.

As I said in my last post, I had disabled the record selection criteria, which stopped the report from crashing, so I decided to concentrate my efforts on the parameters I was using.

All the parameters in question used range values and the check box to allow multiple values was checked. If I uncheck the 'allow multiple values' check box all the reports work fine.

The strange thing about this is that all these reports were working prior to the database changes, using multiple range parameters, but now do not.

I have not tried constructing a new report to see if I can replicate the problem, but will, if I can claw back some of the time I have lost on this problem.

Have you any experience of this? By the way, all the offending parameters were of data type DateTime and I am reporting from an Oracle database

 

[kenhamady]

Haven't seen this, and can't think of why the database change would affect it, unless you changed platforms. What was the change? Did the datatype change in any way? Ken Hamady

http://www.kenhamady.com/

On-site custom Crystal Reports Training and Consulting.
Quick Reference Guide to using Crystal in VB.

 

[WarrenTheWindmill]

New fields had been added to the database. Nothing of significance had changed, at least I don't think so. I will try and re create the problem at some point but for now must press on with the project

Thanks again