Hi folks, I'd like to hear from some of you who have implemented systems that allow for record-level access control in a 4D database. This is the sort of thing where we want to prevent unauthorized users from seeing or inferring the 'restricted' records.
Theoretically it's pretty easy - include a field on relevant tables called 'restricted' or some such and the rules are you filter those records out if the user's permission doesn't allow them. Simple enough but, as we know, there be devils there. Maybe it's a whole different approach to the structure? I want to hear about the details of what it took to make that work with respect to related records, queries on related records, sorting and so on. -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
