Re: MS Access 97 Security questions
- From: "Joan Wild" <jwild@xxxxxxxxxxxxxxxx>
- Date: Thu, 19 Apr 2007 10:25:49 -0400
<jliebman@xxxxxxxxxxxxxxx> wrote in message
news:1176990582.204356.33550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Joan,
Perhaps I didnt clearly state the problem - users all over the
building are using the application in question - its just that it
cannot be maintained or modified except on the creator's PC using the
creator's userid and password - does that sound like an MDW file
problem, or is it the result of the database objects ownership
settings, or something else entirely?
It sounds like the developer secured it so that the Users Group has some
limited permissions (enough to use it, but not change design). This would
allow the users to use the mdb without needing to login - they are using
their standard system.mdw and being silently logged in as 'Admin', which is
a member of the Users Group and so gets those permissions.
When you need to actually make design changes, you need to login using the
secure mdw on the developer's computer; using that mdw and logging in as a
user that is a member of the Admins Group, allows you to make the changes.
You'd then assign the necessary permissions to the Users Group and deploy.
The users in this case don't need to use the secure mdw.
--
Joan Wild
Microsoft Access MVP
.
- References:
- MS Access 97 Security questions
- From: jliebman
- Re: MS Access 97 Security questions
- From: Joan Wild
- Re: MS Access 97 Security questions
- From: jliebman
- MS Access 97 Security questions
- Prev by Date: Re: MS Access 97 Security questions
- Next by Date: Password on front and backend
- Previous by thread: Re: MS Access 97 Security questions
- Next by thread: Password on front and backend
- Index(es):
Relevant Pages
|
