"Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
> Hi everyone! Using A02 on XP. I have user level security working with
> multiple frontend DB's and one backend DB with ALL the tables.  One
> frontend
> DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the backend
> DB
> and linked to the frontend DB.  I've created a group 'Survey' with every
> freakin' permission EXCEPT delete rights and I'll be darned but on my data
> entry form, my group 'Survey' cannot add records but I can (I'm in the
> master
> group 'Admin' which has all power). I have even gone into the backend and
> given full administrative (with delete) rights and STILL I can't get the
> little asterisk to appear for my 'Survey' group.  I've run into this in
> the
> past and usually just keep banging in permissions (probably too many)
> until
> it works but I'm tired of this. I'd love it if someone had some
> information
> for me that will allow me to fix this problem. (Yes, I've made sure "Allow
> Additions" is Yes in properties.)
>
> Thanks in advance for any help or advice.  Luv u guys!!!
>
> --
> Bonnie W. Anderson
> Cincinnati, OH

"Pieter Wijnen" wrote:

> Here are all relevant permissions
>
> Sqlconstant Constant Value Description
>  dbSecCreate 1 The user can create new documents (not valid for Document
> objects).
>  dbSecDBAdmin 8 The user can replicate a database and change the database
> password (not valid for Document objects).
>  dbSecDBCreate 1 The user can create new databases. This option is valid
> only on the Databases container in the workgroup information file
> (System.mdw).
>  dbSecDBExclusive 4 The user has exclusive access to the database.
>  dbSecDBOpen 2 The user can open the database.
>  dbSecDelete 65536 The user can delete the object.
> DELETE dbSecDeleteData 128 The user can delete records.
>  dbSecFullAccess 1048575 The user has full access to the object.
> INSERT dbSecInsertData 32 The user can add records.
>  dbSecNoAccess 0 The user doesn't have access to the object (not valid for
> Document objects).
> SELECT dbSecReadData 20 The user can retrieve data from the Document object.
>  dbSecReadDef 4 The user can read the table definition, including column and
> index information.
>  dbSecReadSec 131072 The user can read the object's security-related
> information.
> UPDATE dbSecReplaceData 64 The user can modify records.
>  dbSecWriteDef 65548 The user can modify or delete the table definition,
> including column and index information.
>  dbSecWriteSec 262144 The user can alter access permissions.
>
> you can therefore execute this (at least in the BE):
>
> Dim Doc As DAO.Document
>
> Set Doc = CurrentDb.Containers("Tables").Documents("MyTable")
> Doc.UserName = "Survey"
> Doc.Permissions = dbSecInsertData + dbSecReadData + dbSecReplaceData
>
> HtH
>
> Pieter
>
> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
> news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
> > Hi everyone! Using A02 on XP. I have user level security working with
> > multiple frontend DB's and one backend DB with ALL the tables.  One
> > frontend
> > DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the backend
> > DB
> > and linked to the frontend DB.  I've created a group 'Survey' with every
> > freakin' permission EXCEPT delete rights and I'll be darned but on my data
> > entry form, my group 'Survey' cannot add records but I can (I'm in the
> > master
> > group 'Admin' which has all power). I have even gone into the backend and
> > given full administrative (with delete) rights and STILL I can't get the
> > little asterisk to appear for my 'Survey' group.  I've run into this in
> > the
> > past and usually just keep banging in permissions (probably too many)
> > until
> > it works but I'm tired of this. I'd love it if someone had some
> > information
> > for me that will allow me to fix this problem. (Yes, I've made sure "Allow
> > Additions" is Yes in properties.)
> >
> > Thanks in advance for any help or advice.  Luv u guys!!!
> >
> > --
> > Bonnie W. Anderson
> > Cincinnati, OH
>
>
>

"Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
news:810151A5-0769-45EA-AD96-ADD9B102D59A@microsoft.com...
> Hi Pieter,
>
> Thank you very much for the reply.  However, I am nowhere near the level
> of
> knowing what to do with what you wrote.
>
> I discovered that my form was pulling the table as it's control source
> rather than a query on the table.  I queried my table rather than using
> the
> table.
>
> Thanks again.
> --
> Bonnie W. Anderson
> Cincinnati, OH
>
>
> "Pieter Wijnen" wrote:
>
>> Here are all relevant permissions
>>
>> Sqlconstant Constant Value Description
>>  dbSecCreate 1 The user can create new documents (not valid for Document
>> objects).
>>  dbSecDBAdmin 8 The user can replicate a database and change the database
>> password (not valid for Document objects).
>>  dbSecDBCreate 1 The user can create new databases. This option is valid
>> only on the Databases container in the workgroup information file
>> (System.mdw).
>>  dbSecDBExclusive 4 The user has exclusive access to the database.
>>  dbSecDBOpen 2 The user can open the database.
>>  dbSecDelete 65536 The user can delete the object.
>> DELETE dbSecDeleteData 128 The user can delete records.
>>  dbSecFullAccess 1048575 The user has full access to the object.
>> INSERT dbSecInsertData 32 The user can add records.
>>  dbSecNoAccess 0 The user doesn't have access to the object (not valid
>> for
>> Document objects).
>> SELECT dbSecReadData 20 The user can retrieve data from the Document
>> object.
>>  dbSecReadDef 4 The user can read the table definition, including column
>> and
>> index information.
>>  dbSecReadSec 131072 The user can read the object's security-related
>> information.
>> UPDATE dbSecReplaceData 64 The user can modify records.
>>  dbSecWriteDef 65548 The user can modify or delete the table definition,
>> including column and index information.
>>  dbSecWriteSec 262144 The user can alter access permissions.
>>
>> you can therefore execute this (at least in the BE):
>>
>> Dim Doc As DAO.Document
>>
>> Set Doc = CurrentDb.Containers("Tables").Documents("MyTable")
>> Doc.UserName = "Survey"
>> Doc.Permissions = dbSecInsertData + dbSecReadData + dbSecReplaceData
>>
>> HtH
>>
>> Pieter
>>
>> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
>> news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
>> > Hi everyone! Using A02 on XP. I have user level security working with
>> > multiple frontend DB's and one backend DB with ALL the tables.  One
>> > frontend
>> > DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the
>> > backend
>> > DB
>> > and linked to the frontend DB.  I've created a group 'Survey' with
>> > every
>> > freakin' permission EXCEPT delete rights and I'll be darned but on my
>> > data
>> > entry form, my group 'Survey' cannot add records but I can (I'm in the
>> > master
>> > group 'Admin' which has all power). I have even gone into the backend
>> > and
>> > given full administrative (with delete) rights and STILL I can't get
>> > the
>> > little asterisk to appear for my 'Survey' group.  I've run into this in
>> > the
>> > past and usually just keep banging in permissions (probably too many)
>> > until
>> > it works but I'm tired of this. I'd love it if someone had some
>> > information
>> > for me that will allow me to fix this problem. (Yes, I've made sure
>> > "Allow
>> > Additions" is Yes in properties.)
>> >
>> > Thanks in advance for any help or advice.  Luv u guys!!!
>> >
>> > --
>> > Bonnie W. Anderson
>> > Cincinnati, OH
>>
>>
>>

"Pieter Wijnen" wrote:

> so the permissions on the query was wrong then?
>
> Pieter
>
> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
> news:810151A5-0769-45EA-AD96-ADD9B102D59A@microsoft.com...
> > Hi Pieter,
> >
> > Thank you very much for the reply.  However, I am nowhere near the level
> > of
> > knowing what to do with what you wrote.
> >
> > I discovered that my form was pulling the table as it's control source
> > rather than a query on the table.  I queried my table rather than using
> > the
> > table.
> >
> > Thanks again.
> > --
> > Bonnie W. Anderson
> > Cincinnati, OH
> >
> >
> > "Pieter Wijnen" wrote:
> >
> >> Here are all relevant permissions
> >>
> >> Sqlconstant Constant Value Description
> >>  dbSecCreate 1 The user can create new documents (not valid for Document
> >> objects).
> >>  dbSecDBAdmin 8 The user can replicate a database and change the database
> >> password (not valid for Document objects).
> >>  dbSecDBCreate 1 The user can create new databases. This option is valid
> >> only on the Databases container in the workgroup information file
> >> (System.mdw).
> >>  dbSecDBExclusive 4 The user has exclusive access to the database.
> >>  dbSecDBOpen 2 The user can open the database.
> >>  dbSecDelete 65536 The user can delete the object.
> >> DELETE dbSecDeleteData 128 The user can delete records.
> >>  dbSecFullAccess 1048575 The user has full access to the object.
> >> INSERT dbSecInsertData 32 The user can add records.
> >>  dbSecNoAccess 0 The user doesn't have access to the object (not valid
> >> for
> >> Document objects).
> >> SELECT dbSecReadData 20 The user can retrieve data from the Document
> >> object.
> >>  dbSecReadDef 4 The user can read the table definition, including column
> >> and
> >> index information.
> >>  dbSecReadSec 131072 The user can read the object's security-related
> >> information.
> >> UPDATE dbSecReplaceData 64 The user can modify records.
> >>  dbSecWriteDef 65548 The user can modify or delete the table definition,
> >> including column and index information.
> >>  dbSecWriteSec 262144 The user can alter access permissions.
> >>
> >> you can therefore execute this (at least in the BE):
> >>
> >> Dim Doc As DAO.Document
> >>
> >> Set Doc = CurrentDb.Containers("Tables").Documents("MyTable")
> >> Doc.UserName = "Survey"
> >> Doc.Permissions = dbSecInsertData + dbSecReadData + dbSecReplaceData
> >>
> >> HtH
> >>
> >> Pieter
> >>
> >> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
> >> news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
> >> > Hi everyone! Using A02 on XP. I have user level security working with
> >> > multiple frontend DB's and one backend DB with ALL the tables.  One
> >> > frontend
> >> > DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the
> >> > backend
> >> > DB
> >> > and linked to the frontend DB.  I've created a group 'Survey' with
> >> > every
> >> > freakin' permission EXCEPT delete rights and I'll be darned but on my
> >> > data
> >> > entry form, my group 'Survey' cannot add records but I can (I'm in the
> >> > master
> >> > group 'Admin' which has all power). I have even gone into the backend
> >> > and
> >> > given full administrative (with delete) rights and STILL I can't get
> >> > the
> >> > little asterisk to appear for my 'Survey' group.  I've run into this in
> >> > the
> >> > past and usually just keep banging in permissions (probably too many)
> >> > until
> >> > it works but I'm tired of this. I'd love it if someone had some
> >> > information
> >> > for me that will allow me to fix this problem. (Yes, I've made sure
> >> > "Allow
> >> > Additions" is Yes in properties.)
> >> >
> >> > Thanks in advance for any help or advice.  Luv u guys!!!
> >> >
> >> > --
> >> > Bonnie W. Anderson
> >> > Cincinnati, OH
> >>
> >>
> >>
>
>
>

"Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message news:A27269A0-C0EA-444D-8FE3-9651CD96095A@microsoft.com...
> Hi Pieter,
>
> I was linking the form's control source directly to the table which had no
> permissions rather than to a query which does have permissions.
>
> Thanks for trying to help.  I appreciate your time.
> --
> Bonnie W. Anderson
> Cincinnati, OH
>
>
> "Pieter Wijnen" wrote:
>
>> so the permissions on the query was wrong then?
>>
>> Pieter
>>
>> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
>> news:810151A5-0769-45EA-AD96-ADD9B102D59A@microsoft.com...
>> > Hi Pieter,
>> >
>> > Thank you very much for the reply.  However, I am nowhere near the level
>> > of
>> > knowing what to do with what you wrote.
>> >
>> > I discovered that my form was pulling the table as it's control source
>> > rather than a query on the table.  I queried my table rather than using
>> > the
>> > table.
>> >
>> > Thanks again.
>> > --
>> > Bonnie W. Anderson
>> > Cincinnati, OH
>> >
>> >
>> > "Pieter Wijnen" wrote:
>> >
>> >> Here are all relevant permissions
>> >>
>> >> Sqlconstant Constant Value Description
>> >>  dbSecCreate 1 The user can create new documents (not valid for Document
>> >> objects).
>> >>  dbSecDBAdmin 8 The user can replicate a database and change the database
>> >> password (not valid for Document objects).
>> >>  dbSecDBCreate 1 The user can create new databases. This option is valid
>> >> only on the Databases container in the workgroup information file
>> >> (System.mdw).
>> >>  dbSecDBExclusive 4 The user has exclusive access to the database.
>> >>  dbSecDBOpen 2 The user can open the database.
>> >>  dbSecDelete 65536 The user can delete the object.
>> >> DELETE dbSecDeleteData 128 The user can delete records.
>> >>  dbSecFullAccess 1048575 The user has full access to the object.
>> >> INSERT dbSecInsertData 32 The user can add records.
>> >>  dbSecNoAccess 0 The user doesn't have access to the object (not valid
>> >> for
>> >> Document objects).
>> >> SELECT dbSecReadData 20 The user can retrieve data from the Document
>> >> object.
>> >>  dbSecReadDef 4 The user can read the table definition, including column
>> >> and
>> >> index information.
>> >>  dbSecReadSec 131072 The user can read the object's security-related
>> >> information.
>> >> UPDATE dbSecReplaceData 64 The user can modify records.
>> >>  dbSecWriteDef 65548 The user can modify or delete the table definition,
>> >> including column and index information.
>> >>  dbSecWriteSec 262144 The user can alter access permissions.
>> >>
>> >> you can therefore execute this (at least in the BE):
>> >>
>> >> Dim Doc As DAO.Document
>> >>
>> >> Set Doc = CurrentDb.Containers("Tables").Documents("MyTable")
>> >> Doc.UserName = "Survey"
>> >> Doc.Permissions = dbSecInsertData + dbSecReadData + dbSecReplaceData
>> >>
>> >> HtH
>> >>
>> >> Pieter
>> >>
>> >> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
>> >> news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
>> >> > Hi everyone! Using A02 on XP. I have user level security working with
>> >> > multiple frontend DB's and one backend DB with ALL the tables.  One
>> >> > frontend
>> >> > DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the
>> >> > backend
>> >> > DB
>> >> > and linked to the frontend DB.  I've created a group 'Survey' with
>> >> > every
>> >> > freakin' permission EXCEPT delete rights and I'll be darned but on my
>> >> > data
>> >> > entry form, my group 'Survey' cannot add records but I can (I'm in the
>> >> > master
>> >> > group 'Admin' which has all power). I have even gone into the backend
>> >> > and
>> >> > given full administrative (with delete) rights and STILL I can't get
>> >> > the
>> >> > little asterisk to appear for my 'Survey' group.  I've run into this in
>> >> > the
>> >> > past and usually just keep banging in permissions (probably too many)
>> >> > until
>> >> > it works but I'm tired of this. I'd love it if someone had some
>> >> > information
>> >> > for me that will allow me to fix this problem. (Yes, I've made sure
>> >> > "Allow
>> >> > Additions" is Yes in properties.)
>> >> >
>> >> > Thanks in advance for any help or advice.  Luv u guys!!!
>> >> >
>> >> > --
>> >> > Bonnie W. Anderson
>> >> > Cincinnati, OH
>> >>
>> >>
>> >>
>>
>>
>>

"Joan Wild" wrote:

> It's unclear whether you've resolved your problem?
>
> Users need the necessary permissions on the query that the form is based on.  If the query is set to RWOP (run with owner permissions), then users don't need any permissions on the tables.
>
> --
> Joan Wild
> Microsoft Access MVP
> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message news:A27269A0-C0EA-444D-8FE3-9651CD96095A@microsoft.com...
> > Hi Pieter,
> >
> > I was linking the form's control source directly to the table which had no
> > permissions rather than to a query which does have permissions.
> >
> > Thanks for trying to help.  I appreciate your time.
> > --
> > Bonnie W. Anderson
> > Cincinnati, OH
> >
> >
> > "Pieter Wijnen" wrote:
> >
> >> so the permissions on the query was wrong then?
> >>
> >> Pieter
> >>
> >> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
> >> news:810151A5-0769-45EA-AD96-ADD9B102D59A@microsoft.com...
> >> > Hi Pieter,
> >> >
> >> > Thank you very much for the reply.  However, I am nowhere near the level
> >> > of
> >> > knowing what to do with what you wrote.
> >> >
> >> > I discovered that my form was pulling the table as it's control source
> >> > rather than a query on the table.  I queried my table rather than using
> >> > the
> >> > table.
> >> >
> >> > Thanks again.
> >> > --
> >> > Bonnie W. Anderson
> >> > Cincinnati, OH
> >> >
> >> >
> >> > "Pieter Wijnen" wrote:
> >> >
> >> >> Here are all relevant permissions
> >> >>
> >> >> Sqlconstant Constant Value Description
> >> >>  dbSecCreate 1 The user can create new documents (not valid for Document
> >> >> objects).
> >> >>  dbSecDBAdmin 8 The user can replicate a database and change the database
> >> >> password (not valid for Document objects).
> >> >>  dbSecDBCreate 1 The user can create new databases. This option is valid
> >> >> only on the Databases container in the workgroup information file
> >> >> (System.mdw).
> >> >>  dbSecDBExclusive 4 The user has exclusive access to the database.
> >> >>  dbSecDBOpen 2 The user can open the database.
> >> >>  dbSecDelete 65536 The user can delete the object.
> >> >> DELETE dbSecDeleteData 128 The user can delete records.
> >> >>  dbSecFullAccess 1048575 The user has full access to the object.
> >> >> INSERT dbSecInsertData 32 The user can add records.
> >> >>  dbSecNoAccess 0 The user doesn't have access to the object (not valid
> >> >> for
> >> >> Document objects).
> >> >> SELECT dbSecReadData 20 The user can retrieve data from the Document
> >> >> object.
> >> >>  dbSecReadDef 4 The user can read the table definition, including column
> >> >> and
> >> >> index information.
> >> >>  dbSecReadSec 131072 The user can read the object's security-related
> >> >> information.
> >> >> UPDATE dbSecReplaceData 64 The user can modify records.
> >> >>  dbSecWriteDef 65548 The user can modify or delete the table definition,
> >> >> including column and index information.
> >> >>  dbSecWriteSec 262144 The user can alter access permissions.
> >> >>
> >> >> you can therefore execute this (at least in the BE):
> >> >>
> >> >> Dim Doc As DAO.Document
> >> >>
> >> >> Set Doc = CurrentDb.Containers("Tables").Documents("MyTable")
> >> >> Doc.UserName = "Survey"
> >> >> Doc.Permissions = dbSecInsertData + dbSecReadData + dbSecReplaceData
> >> >>
> >> >> HtH
> >> >>
> >> >> Pieter
> >> >>
> >> >> "Bonnie A" <bonniely***@discussions.microsoft.com> wrote in message
> >> >> news:46B34CF9-D713-4D2D-8A19-D542514EBF7D@microsoft.com...
> >> >> > Hi everyone! Using A02 on XP. I have user level security working with
> >> >> > multiple frontend DB's and one backend DB with ALL the tables.  One
> >> >> > frontend
> >> >> > DB is called Survey.mdb.  The main table, tSurveyAug2007 is in the
> >> >> > backend
> >> >> > DB
> >> >> > and linked to the frontend DB.  I've created a group 'Survey' with
> >> >> > every
> >> >> > freakin' permission EXCEPT delete rights and I'll be darned but on my
> >> >> > data
> >> >> > entry form, my group 'Survey' cannot add records but I can (I'm in the
> >> >> > master
> >> >> > group 'Admin' which has all power). I have even gone into the backend
> >> >> > and
> >> >> > given full administrative (with delete) rights and STILL I can't get
> >> >> > the
> >> >> > little asterisk to appear for my 'Survey' group.  I've run into this in
> >> >> > the
> >> >> > past and usually just keep banging in permissions (probably too many)
> >> >> > until
> >> >> > it works but I'm tired of this. I'd love it if someone had some
> >> >> > information
> >> >> > for me that will allow me to fix this problem. (Yes, I've made sure
> >> >> > "Allow
> >> >> > Additions" is Yes in properties.)
> >> >> >
> >> >> > Thanks in advance for any help or advice.  Luv u guys!!!
> >> >> >
> >> >> > --
> >> >> > Bonnie W. Anderson
> >> >> > Cincinnati, OH
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>