Re: [Emerald] Me again...
David Routh ( firstname.lastname@example.org )
Wed, 19 Jan 2000 18:34:41 -0600
At 03:00 PM 9/19/1999 -0700, you wrote:
>David Routh wrote:
>> >> Also, what I really need to restrict is some of the Billing Groups our
>> >> Operators see... that's why I'm thinking I could work with a new
>> >> is set like the EmeraldSecure group.
>> >Unfortunately, you would have to use the EmeraldSecure group to do that.
>> What would I break if I selectively removed some of the Delete, Insert
>> and/or Update check marks in the Permissions for EmeraldSecure? And I'm
>> thinking I'd do that for the v*** Objects... like "vMasterAccounts".
>> Would unchecking Delete in "vActions" stop any deleting?
>Thats actually the way you should do it. For EmeraldSecure, they
>usuaully don't have access to the Table, where a view exists with the
>same name (except with a v in front of it). Remove delete from
>those objects (and insert to prevent adding) and it will do what you
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc. www.iea-software.com
>For more information about this list (including removal) go to:
For more information about this list (including removal) go to: