Hello:
We are in the process of upgrading to BI4 and Crystal 2016. We are having an issue with our existing reports - in the new environment, when reports are run on demand they run correctly. We are finding, however, that when we schedule reports some of the subreports are missing linking info and so are doing full table scans. For example, when running on demand we might see in the back end that the subreport is running a statement that includes tablename.fieldvalue = 'Peterson'. Then, when scheduling the same report we'll see the statement running for the same report now doesn't include this line and so the whole tablename table is being scannned.
Any thoughts on what might be causing this?
TIA.
Holly
We are in the process of upgrading to BI4 and Crystal 2016. We are having an issue with our existing reports - in the new environment, when reports are run on demand they run correctly. We are finding, however, that when we schedule reports some of the subreports are missing linking info and so are doing full table scans. For example, when running on demand we might see in the back end that the subreport is running a statement that includes tablename.fieldvalue = 'Peterson'. Then, when scheduling the same report we'll see the statement running for the same report now doesn't include this line and so the whole tablename table is being scannned.
Any thoughts on what might be causing this?
TIA.
Holly