<< This is a clear indication that the problem is in your view definition. What you have confirmed is that it is not the report printing that takes the time, but the retrieval of data from the view. >>
It sounds like the opposite to me. PROJECTing or SELECTing the data is fast, it's only when used in the report that it's slow. To me, that means one of two thing: 1. A problem with code or an expression in the report that either is missing an index, or is being evaluated too often, or something like that. 2. Something inherent in simply loading the report format. I'm wondering if perhaps something has happened to the #4 file to make it much slower to simply retrieve the report definition. If so, an UNLOAD ALL and rebuild of the database may be necessary to recreate the #4 file from scratch. -- Larry
