One other possibility if you don't want to use the "*" feature which involves exception programming is to include a record in the table for every User/Owner/Client entry and then add another boolean field called Live_Status which would allow access to the client or not. This makes any queries easy to generate as you would include where Live_Status = true (or TSQL equivalent) when extracting any query information.
Dave -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Andrew Stirling Sent: 18 January 2017 16:05 To: [email protected] Subject: Restrict access to multi clients I'm trying to get an online system working that allows: Users to log in to an Owner organisation ie firm of accountants. Owner to display list of clients to work on. So I have that working with User: Id owner_id Owner Id Clients Id owner_id User has owner relationship and owner has client relationship. Thus User can choose from a list of clients to work on. HOWEVER what I want is to be able to restrict the clients that the User can see. How do I go about that? -- Kind regards Andrew Stirling 01250 870397 07910467915 [email protected] http://www.calcpay.co.uk --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
