Should Have Permission, but Doesn't (?)

[tbl]

In a secured, split Access 2000 / 2002 db, when I log in as
a member of a group that has run permission for all the
forms, I get a permissions error:

"Record(s) cannot be read; no read permission
on 'tblCountDetail'".

The forms are all based on querys with 'Run with owner's'
property, and all the combos are based on querys with that
property.

This user/group was working ok a few months ago, and I've
made some changes to form code since then, but I don't
recall changing anything more structural. The code changes
involve setting some DefaultValues conditionally, and they
do include a dLookup statement (with a 'where' clause).
Could that be the problem?

All the forms work fine with an Admin level user.

What else could be wrong? (drawing a complete blank at the
moment!)

 

[Joan Wild]

In a secured, split Access 2000 / 2002 db, when I log in as
a member of a group that has run permission for all the
forms, I get a permissions error:

"Record(s) cannot be read; no read permission
on 'tblCountDetail'".

The forms are all based on querys with 'Run with owner's'
property, and all the combos are based on querys with that
property.

Are these actually saved queries, or SQL statements?

This user/group was working ok a few months ago, and I've
made some changes to form code since then, but I don't
recall changing anything more structural. The code changes
involve setting some DefaultValues conditionally, and they
do include a dLookup statement (with a 'where' clause).
Could that be the problem?

Only if tblCountDetail is involved in the DLookup statement, and users don't have permission on the table.

You need to narrow it down to where tblCountDetail is being used - recordsource for the form, combo/listbox, code, domain function.

 

[tbl]

Are these actually saved queries, or SQL statements?


Only if tblCountDetail is involved in the DLookup statement, and users don't have permission on the table.

You need to narrow it down to where tblCountDetail is being used - recordsource for the form, combo/listbox, code, domain function.

Thanks Joan.

The Where statement does involve that table and the user
doesn't have permission for that table. I was hoping that
the form code would be treated with Admin permissions.

Do I need to give that group permissions on both the back
end table *and* the front end link to it, or just one or the
other? Or is there some way to do something fancy with an
"owner" type of property... or something?

 

[Joan Wild]

Just create a RWOP query SELECT * FROM tblCountDetail (maybe you already have one). I sometimes create a base RWOP query for every table. All subsequent queries/forms/reports are based on these base queries - makes things simple.

You can use DLookup against a query - you're not limited to tables for the <domain>.

 

[tbl]

Just create a RWOP query SELECT * FROM tblCountDetail (maybe you already have one). I sometimes create a base RWOP query for every table. All subsequent queries/forms/reports are based on these base queries - makes things simple.

You can use DLookup against a query - you're not limited to tables for the <domain>.

Ahah!

Thanks Joan.

 

[Joan Wild]

Ahah!

Thanks Joan.

You're welcome - gotta love those 'ahah' moments.