Subform not displayed unless database owner

[joan.edington]

Hi,

I have an Access 2003 DB which has a form and linked subform. I
designed the DB with no security and had no problems. However, when I
tied the security down to only allowing myself design permissions and
everyone else restricted ones, my own user with permissions to do
absolutely everything has a problem. The subform does not display. It
does if anyone else uses the DB.

What may sound odd is the way I have security set up. Several members
of staff have their own simple databases and there is no corporate
Access Workgroup security in place. Since the default user is admin, I
have left everyone using that. In my own copy of the workgroup file I
have my own user as well as admin. I have changed things round so that
I have all the permissions and admin is restricted.

When the database was created, admin was the owner and I can't change
it.

Only admin can now see the subform although that user has less
permissions than me.

Can anyone please give me a clue as to why this is happening and,
hopefully, how to get round it?

Thanks.

Joan

 

[Larry Linson]

I have an Access 2003 DB which has a form and linked subform. I
designed the DB with no security and had no problems. However, when I
tied the security down to only allowing myself design permissions and
everyone else restricted ones, my own user with permissions to do
absolutely everything has a problem. The subform does not display. It
does if anyone else uses the DB.

What may sound odd is the way I have security set up. Several members
of staff have their own simple databases and there is no corporate
Access Workgroup security in place. Since the default user is admin, I
have left everyone using that. In my own copy of the workgroup file I
have my own user as well as admin. I have changed things round so that
I have all the permissions and admin is restricted.

When the database was created, admin was the owner and I can't change
it.

Only admin can now see the subform although that user has less
permissions than me.

Can anyone please give me a clue as to why this is happening and,
hopefully, how to get round it?

Your somewhat unorthodox approach to securing the database has, as you seem
to have realized, created the problem for you. But, can you not change the
owner simply by creating your own blank DB, under your security workgroup,
and importing all the objects from the original?

Larry Linson
Microsoft Access MVP