Environment:
Crystal 2008
Oracle 11
Stored Procedure
A stored proc was updated to include a new field which would form a new group in the report. The report has been in production prior to the addition of the fieldfor three months.
Followed the procedure:
=================================================
If it is a new field, when you click on Verify Database you will receive a pop-up message stating…”The database file….has changed. Proceeding to fix up the report.”
Click OK to this message.
The new field added should now appear in your Field Explorer.
If it is a field name change or data type change, when you click on Verify Database under the Database menu you will receive the Mapped Fields dialog box.
==================================================
The EXPECTATION was that the new field would appear in the Field Explorer without any further ado.
In fact, the Verify routinr popped up the Mapped Fields box with the new field in the Unmapped Field quadrant as if there had been a data type change or field name change. Since this was the addition of a new field, I fully expected to see
”The database file….has changed. Proceeding to fix up the report.”
as I have seen over the last 15 years!
Attempts:
Log On/Log Off/ Log On to DB - Verify.... Now the db is up to date, but the field does not show
Changed Datasources - Verify.... The db is up to date, but the field does not show
No matter what has been attempted either on of two things happens:
On a 'clean' versions of the rpt file, tried each 'trick' - no field; but the db is 'up to date'
Saved each iteration, closed down CR, re-started and re-opened each iteration and did a Verify... no joy.
Any experiences similar - and, if so, were you able to overcome this? If so, any suggestions?
Thanks....
Crystal Reports Design/training/Consultation
ecsdata@ecsdata.com
Crystal 2008
Oracle 11
Stored Procedure
A stored proc was updated to include a new field which would form a new group in the report. The report has been in production prior to the addition of the fieldfor three months.
Followed the procedure:
=================================================
If it is a new field, when you click on Verify Database you will receive a pop-up message stating…”The database file….has changed. Proceeding to fix up the report.”
Click OK to this message.
The new field added should now appear in your Field Explorer.
If it is a field name change or data type change, when you click on Verify Database under the Database menu you will receive the Mapped Fields dialog box.
==================================================
The EXPECTATION was that the new field would appear in the Field Explorer without any further ado.
In fact, the Verify routinr popped up the Mapped Fields box with the new field in the Unmapped Field quadrant as if there had been a data type change or field name change. Since this was the addition of a new field, I fully expected to see
”The database file….has changed. Proceeding to fix up the report.”
as I have seen over the last 15 years!
Attempts:
Log On/Log Off/ Log On to DB - Verify.... Now the db is up to date, but the field does not show
Changed Datasources - Verify.... The db is up to date, but the field does not show
No matter what has been attempted either on of two things happens:
On a 'clean' versions of the rpt file, tried each 'trick' - no field; but the db is 'up to date'
Saved each iteration, closed down CR, re-started and re-opened each iteration and did a Verify... no joy.
Any experiences similar - and, if so, were you able to overcome this? If so, any suggestions?
Thanks....
Crystal Reports Design/training/Consultation
ecsdata@ecsdata.com