>To expand on what Lutz said, the only reason you ever need to create a random name for a cursor is if a _single_ user can run the code that creates more than once at the same time. For example, if a form that isn't using private data sessions creates a cursor and the user can run that form more than once.
>
>Since a report is essentially a modal activity (well, preview is modal and running the report prevents the user from doing anything else until it completes, so is functionally modal), there's no reason to use a random name for a cursor for a report.
>
>Tamar

Hi Tamar,

There might be a theoretical problem with reports chained (so you run the same report in a loop in some generic printer class for different pre created cursors) with related cursors.
I would solve this in having all in one wide cursor, and not go for the alias at all, but tastes are different.

@Dimitry, just btw:
EVALUATE in report fields is a pain. As any function there. It runs every time the field is reached, what ends up very slow.