Hello Anthony,

First of all, thank you for taking the time to answer my question.

The reason I run the reports under Windows Integrated Security is because we have enabled some row-level security mechanisms where the IS_MEMBER() method is used through a JOIN on the views requested and only those rows are returned which the user is allowed to see. So running a report under a general account (as far as I know) eliminates this requirement by my client.

A login trigger will probably do the trick indeed, I will look into this option. Have to be careful with using the login trigger, don't want to lock out everybody 🙂

If there are most design options, I'd love to hear them.