>>>I think what Dave Emerson says is the solution, I haven't met this problem, because I always try to create the cursor with the SELECT .... WHERE... statement and run report on that cursor.
>>>
>>>Nick
>>
>>Nick,
>>
>>I agree. I finding more and more that using cursors for reports solves problems before they hit you in the face.
>>
>>Dave
>
>Just out of curiousity.... are you saying maybe that you prefer using cursors for reports over views? Or just prefer using cursors over the actual tables?

Actually, I have nothing against using actual tables for reports. :)
But in most cases you need subset of records for the particular report,
and here begins the point when I start to use parameterized views or SELECT... WHERE ... INTO CURSOR...

The only thing I ask from actual tables, views or cursors - that they must contain only records I need for report... :)

Nick