The development folks would like to be able to view the procedures, packages, etc., on a production reporting database, but we do *NOT* want them to be able change anything. This is sort of like a "read only" access to packages, procedures, triggers, etc. I would think this would be like a "select any view" but I don't see any thing there. Can this be done by granting some sort of privs to a role and then giving them the role? Michael Kline Database Administration SunTrust Technology Center 1030 Wilmer Avenue Richmond, Virginia 23227 Outside 804.261.9446 STNet 643.9446 Cell 804.744.1545 <mailto:michael.kline@xxxxxxxxxxxx> michael.kline@xxxxxxxxxxxx ************************************************ The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. [ST:A234] ************************************************ -- //www.freelists.org/webpage/oracle-l