>Thanks. Maybe I didn't make myself clear. What I want to try to prevent is some user that has access to the subscription application but doesn't have right to the fundraising data getting an error should they try to run the report. I will add a feature to the security maintenance screen which is only accessible by the system administor who can specify who have the rights. I will first check to see if the user have right to the fundraising data and if they don't then I will inform them. The user don't have access to the security maintenance screen and therefore won't be able to change their rights. Thanks again - I thought I was headed in the right direction but just want to check it out since I had done this before.

Milt,

I'm thinking, if person doesn't have rights to print this report, he/she should not even see this button (menu choice), otherwise this person could be offended.
Unfortunately, there is no simple way to hide menu (don't know, if OOP menu with visible property is already listed in Toledo Wish list).

Another thing, which is my long standing wish - add visible property to page object. Mike Helland has a class here, which has this feature, but it would be nice, if native Page would have it.