We are running various reports in Crystal and accessing a SQL Server database. All of a sudden, reports are returning huge numbers of results rather than the correct ones. This does not always happen... sometimes, rebooting the PC that the report is running on (NOT where the SQL Server Database is running) allows the report to run correctly, at least for a time, before giving invalid data again.
I have been looking at a particular report and do not know if the others with problems are similar.
In this case, the report pulls data from a view, which in turn uses a sub-view. In the sub-view there is an inner join to a table and a condition that one of the fields in that table "IS NULL". Since it does some grouping, the condition is a "HAVING", but I have tried it as a "WHERE" clause without any change in the results.
This report DID work reliably, but it has suddenly started including records which do NOT have a NULL value in that field.
I have checked the actual data and, sure enough, there is valid data in the field.
The field concerned was updated years ago and so there is no way that the report could be pointing at old data.
The possible causes that I can think of include;
1. A timeout on the view or subview which, rather than causing the overall query to fail, causes it to return data that is invalid.
2. Some sort of Indexing problem.
Any ideas as to what else could be causing this or how it might either be investigated further or fixed ?
We are submitting a trouble ticket to Microsoft. I am also going to submit this question in the Crystal forum, although I have tried running the views through Access and gotten the same results, so I am pretty certain that it is not a Crystal problem per se.
Thanks.
I have been looking at a particular report and do not know if the others with problems are similar.
In this case, the report pulls data from a view, which in turn uses a sub-view. In the sub-view there is an inner join to a table and a condition that one of the fields in that table "IS NULL". Since it does some grouping, the condition is a "HAVING", but I have tried it as a "WHERE" clause without any change in the results.
This report DID work reliably, but it has suddenly started including records which do NOT have a NULL value in that field.
I have checked the actual data and, sure enough, there is valid data in the field.
The field concerned was updated years ago and so there is no way that the report could be pointing at old data.
The possible causes that I can think of include;
1. A timeout on the view or subview which, rather than causing the overall query to fail, causes it to return data that is invalid.
2. Some sort of Indexing problem.
Any ideas as to what else could be causing this or how it might either be investigated further or fixed ?
We are submitting a trouble ticket to Microsoft. I am also going to submit this question in the Crystal forum, although I have tried running the views through Access and gotten the same results, so I am pretty certain that it is not a Crystal problem per se.
Thanks.