Re: Limiting Client Access

[rob@xxxxxxxxx]

There are things called "exit points".  From these you can write a program 
to ensure that user XYZ is only downloading file ABC from library EFG. If, 
instead of rolling your own, you'd rather purchase a product, here is a 
list of vendors:
http://faq.midrange.com/data/cache/198.html

Be careful, we told people that they could only download this one file 
generated by Query.  They quickly figured out all they had to do was have 
their favorite query generate a file of the same name in the same library. 
 Our users aren't stupid, (and evidently, not respectful).

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Jose Vega" <jvega@platt.com>
Sent by: midrange-l-bounces@midrange.com
01/28/2003 07:18 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        Limiting Client Access





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.

TIA,

Jose

_______________________________________________
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.