RE: Limiting Client Access

[Emilio Padilla - Sistemática Int. <EPADILLA@xxxxxxxxxxxxxxxxxx>]

I would add a CHGUSRAUD for any external user. 

EMILIO PADILLA T

        -----Original Message-----
        From:   Chris Bipes [SMTP:chris.bipes@cross-check.com]
        Sent:   Wednesday, January 29, 2003 10:23 AM
        To:     'Midrange Systems Technical Discussion'
        Subject:        RE: Limiting Client Access

        Create a library that they have Read Only access to and place
limited views
        of your data their.  (LF's with only the fields you want them to see
and
        optionally select/omit to restrict record access).  The views can be
created
        as read only as well.

        Christopher K. Bipes      mailto:Chris.Bipes@Cross-Check.com
        Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
        CrossCheck, Inc.          http://www.cross-check.com
        6119 State Farm Drive     Phone: 707 586-0551 x 1102
        Rohnert Park CA  94928    Fax: 707 586-1884


        -----Original Message-----
        From: Jose Vega [mailto:jvega@platt.com]

        Hello,

        One of our VPs wants us to give users client access
        but our concern is the access they will have to the entire database.
        Has anyone come across a situation where they have end-users needing
        file transfer capability from client access yet needed to protect
the rest
        of the live data.
         If so how did you handle limiting their access.
        We don't use Object level security.
        _______________________________________________
        This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
        To post a message email: MIDRANGE-L@midrange.com
        To subscribe, unsubscribe, or change list options,
        visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
        or email: MIDRANGE-L-request@midrange.com
        Before posting, please take a moment to review the archives
        at http://archive.midrange.com/midrange-l.