DB change, can't get data any more?

[CraigBest]

Had prepared a report on an oracle 8 database, using the CROR8 ODBC driver. Everything was working fine until this morning, when we found a problem with a field in the table the report uses. After we fixed the change, the report no longer shows any data.

If we browse the fields from the Field object selector or Formula window, we can see the data (field by field) fine. but nothing is filled when the report is run.

Any idea on how I might be able to fix this?

 

[dgillz]

Craig-

Are you saying you modified the database itself? Not the data in the database but the individual field names, lengths, data types and/or properties?

If so you need to verify the database before crystal can read it. Click on Database, verify database. If any of the fields used in the report have changed names, you will be prompted togo through a field-to-field mapping process.

Please let me know if you have any questions.

Software Support for Macola, Crystal Reports and Goldmine
dgilsdorf@mchsi.com

 

[CraigBest]

dgillz,

<< Are you saying you modified the database itself? Not the data in the database but the individual field names, lengths, data types and/or properties?

If so you need to verify the database before crystal can read it. Click on Database, verify database. If any of the fields used in the report have changed names, you will be prompted togo through a field-to-field mapping process.

Please let me know if you have any questions.>>

Sorry, I should have said. Yes, I tried verifying the database, that didn't work. I eventually dropped the tables and reaquired them using the add database table function. After deleting and replacing all of the database fields on the report, it worked again. I tried a lot of things but couldn't get the data to read back out again until I did this.

We made changes to the data table, not the data within. None of the fields used in the report were changed, but we changed the size of one column and deleted another.

I'd still like to get to the bottom of this because I know there will probably be more changes in the future and I don't like the idea of having to rewrite all my reports every time we tweak something.

 

[dgillz]

Database, verify database is a part of crystal reports for exactly the reasons you describe - to avoid deleting and re-adding the database(s). If the verify database routine did not work I am at a loss. I would call Crystal Decisions.

Software Support for Macola, Crystal Reports and Goldmine
dgilsdorf@mchsi.com

 

[kenhamady]

Yes, verify should work. But, you could have tried setting the location of the problem table to another table, and then setting it back to the target table. This would cause CR to do the same amount of work as adding a table but you don't have to re-add fields. You will need to create a temporary table that has all of the same fields in it to use as the intermediate table, otherwise CR would make you remap all of the field. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[chelseatech]

One problem that sometimes occurs when you make DB changes, and then verify the DB is that the table links get droped. So always check those after you've verified. Editor and Publisher of Crystal Clear

http://www.chelseatech.co.nz/pubs.htm