For some rationale justifying why it is the way it is (it's how most db's work): http://www.freelists.org/archives/oracle-l/10-2004/msg00690.html http://www.mssqlcity.com/Articles/Adm/manage_users_permissions.htm#part_4
If you are using assignee group read on fid 1, bring in the assignee group field to the join, retain the fid of the assignee group, then set the permissions of the join fid 1 to assignee group read. Axton Grams On 8/24/07, Phil Murnane <[EMAIL PROTECTED]> wrote: > ** > > Lars: > > I think since the join form has a separate field (ID 1) not inherited from > either base form, then the proper permissions must be manually applied to > the join form's field ID 1. > > Despite this, I agree with you that if a user has no access to a base form > record, then the user should have no access to a derived join form record. > > Just my $0.02, > --Phil > > > ----- Original Message ---- > From: "[EMAIL PROTECTED]" > <[EMAIL PROTECTED]> > To: [email protected] > Sent: Friday, August 24, 2007 8:55:44 AM > Subject: Access question > > ** > > Hi list, suppose permissions are set so that a user can't access a ticket > when searching directly in a form. No access to field 1. > > I have a joinform, users are able to see fields from this 'forbidden entry' > in this join, unexpected, can't be as designed? > > L ars Pettersson > Vattenfall Business Services Nordic AB > Action Request System Engineer (Tabasco) > S-461 88 Trollhättan > Sweden > > Phone +46 520 888 35 Mobil +46 70 608 99 95 > e-mail: [EMAIL PROTECTED] > __20060125_______________________This posting was submitted > with HTML in it___ > > > ________________________________ > Shape Yahoo! in your own image. Join our Network Research Panel today! > __20060125_______________________This posting was > submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
