Admin = form works User = form fails

  • Thread starter Thread starter Al Campagna
  • Start date Start date
A

Al Campagna

This is a real stumper...
I have an ubound main form named frmCreelWaste. It has a combo on it
named cboWarpNo.
I have a subform based on a select query against tblCreelWaste.
The main and sub are linked by Parent = cboWarpNo to Child = WarpNo.

In the .mdw file, there is a Group called WarpGroup, of which WarpRoom
is a member, and...
User WarpRoom has Open/Run permission for both forms.
User WarpRoom has ReadDesign, Read, Update, Insert, Delete for
tblCreelWaste.
WarpGroup has Open/Run permissions for both forms.
WarpGroup has ReadDesign, Read, Update, Insert, Delete for
tblCreelWaste.

As the devloper, and as an Admin, the form works just fine. I can add,
delete, edit subform records. And... the query behind the form is
updateable!
But... if I sign in as WarpRoom, a member of WarpGroup, the subform
opens, but refuses to allow additions, and edits, and... deletions error out
as...
"No delete permission for tblCreelWaste"
and... the query behind the subform is not updateable!

My client has had extensive experience with handling security, and this
same form setup is currently working on other forms of similar design within
this same DB.
I have another similar setup of form/s and security, and WarpRoom can
run those forms with no problems.

What could possibly cause this problem. The form works for admin but
not for a user (with permissions) in a group (with permissions)?
I can find nothing in the setup of either form, or in any of my code for
either form.

Any help appreciated,
Al Campagna
 
OK folks,
Here's what I discovered. This DB has an FE and BE
I, and the client, in our bug shooting, had been giving permissions to
groups and users via the FE Tools/Security.
WarpGroup the Group, and WarpRoom the User,were given permissions as
indicated in previous post. (and below)
When I opened the BE, as user WarpRoom, the table was not updateable,
and the MDW file, when viewed from the BE, indicated that the user and the
group did not have table permission.
I updated the MDW **from the BE ** to...
User WarpRoom has Open/Run permission for both forms.
User WarpRoom has ReadDesign, Read, Update, Insert, Delete for
tblCreelWaste.
WarpGroup has Open/Run permissions for both forms.
WarpGroup has ReadDesign, Read, Update, Insert, Delete for
tblCreelWaste.
Click to expand...
and everything worked like a champ! User WarpRoom can use the form, and
edit the subform... and "this is the best of all possible worlds" :-D

My question now becomes... should all security settings be done from the
BE?
Or at least all the Table/Query security be done from the BE, and
Forms/Reports
security done from the FE?

Thanks for any assistance,
Al
 
Back
Top