Re: [Emerald] Me again...

Dale E. Reed Jr. ( (no email) )
Sun, 19 Sep 1999 15:00:13 -0700

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 group that
> >> 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.

For more information about this list (including removal) go to: