Thanks for the help.
Eric Jensen
At 09:52 AM 12/9/99 -0800, you wrote:
>Chris Melching wrote:
> >
> > I'm having a similar problem. What I am trying to do is this:
> >
> > We have a number of billing groups, with monies deposited from those groups
> > going into different credit card merchant accounts. When I batch a group of
> > credit cards, it bunches all the billing groups together (as it should.)
> >
> > My solution was to create an operator group that ONLY had access to ONE
> > billing group. That way, only those credit cards that I wanted to
> batch for
> > that group would actually be affected. To date, I have been unable to make
> > this work. It's as if the security options I am setting up are not being
> > used at all.
> >
> > Is this a problem with Emerald, our SQL server, or what? Anyone have any
> > ideas?
>
>2.5 is not designed to do complete virtual ISP in this manner (ie,
>billing).
>The groups security was only designed for editing users (ie, limiting
>who
>you can see).
>
>
>--
>
>Dale E. Reed Jr. Emerald and RadiusNT
>__________________________________________
>IEA Software, Inc. www.iea-software.com
>
>For more information about this list (including removal) go to:
>http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart