ACCESS PErmissions Issues

[Sam]

We are using a simple (four field) db that was created in ACCESS 2003 with
an ACCESS 2007 front end on a network using (I believe Windows Server 2003)
and XP Pro PCs User are only supposed to use the drop down in one field to
change data. Some users keep adding data to some fields corrupting the db.
Some of these fields need to edited by the db a support person.

We need to allow users to read only and allow the support staff only to make
changes to the db. Can we do this on the folder leverl or do we need to do
it in the db?

Why should we change the db to ACCESS 2007 from ACCESS 2003?

Thanks,

Sam

 

[Mr. B]

First, I notice that you have a split database format which is good, but from
your post it is not clear if each user has their own front-end on their own
machine. If this is not the case, but all means, you need to have each user
have their own copy of the front-end file on their workstation.

As for not allowing users to do anything except make a selection from a
combo box, you will need to make changes in the front-end to accomplish this.
All you need to do is change the "Locked" property to "yes" for each control
that you do not want them to change the data.

If you can have a version of the front-end that has the desired controls
locked and distribute that version to the ones that do not need to make
changes to these controls. You can also then have a version of the front-end
that does not have these same controls locked and distribute that version to
users that need to be able to make changes to these fields.

-----
HTH
Mr. B
http://www.askdoctoraccess.com/
Doctor Access Downloads Page:
http://www.askdoctoraccess.com/DownloadPage.htm

 

[Sam]

First, I notice that you have a split database format which is good, but
from
your post it is not clear if each user has their own front-end on their
own
machine. If this is not the case, but all means, you need to have each
user
have their own copy of the front-end file on their workstation.

As for not allowing users to do anything except make a selection from a
combo box, you will need to make changes in the front-end to accomplish
this.
All you need to do is change the "Locked" property to "yes" for each
control
that you do not want them to change the data.

If you can have a version of the front-end that has the desired controls
locked and distribute that version to the ones that do not need to make
changes to these controls. You can also then have a version of the
front-end
that does not have these same controls locked and distribute that version
to
users that need to be able to make changes to these fields.

-----
HTH
Mr. B
http://www.askdoctoraccess.com/
Doctor Access Downloads Page:
http://www.askdoctoraccess.com/DownloadPage.htm

The 2003 access db file is stored on a network drive and the front end
Access 2007 (Office 2007)
is on each PC. Now the end users will only have to review the DB for
accuracy and a couple of users
need access to update/edit the db. Why in the world did MS remove user
controls from the 2007 access front end.

 

[James A. Fortune]

If you can have a version of the front-end that has the desired controls
locked and distribute that version to the ones that do not need to make
changes to these controls. You can also then have a version of the front-end
that does not have these same controls locked and distribute that version to
users that need to be able to make changes to these fields.

If you follow that advice, be careful that your databases don't start
breeding like rabbits.

James A. Fortune
(e-mail address removed)

 

[Sam]

If you follow that advice, be careful that your databases don't start

I hope I'm not reading this messages correctly or maybe I haven't described
the problem
adequately but I really seems complicated to me.

All 200 users need to be able to read only the db and a few users need to
make changes to the db.
the db is access 2003 and the front end on each PC is access 2003.

 

[Tony Toews [MVP]]

We are using a simple (four field) db that was created in ACCESS 2003 with
an ACCESS 2007 front end on a network using (I believe Windows Server 2003)
and XP Pro PCs User are only supposed to use the drop down in one field to
change data. Some users keep adding data to some fields corrupting the db.
Some of these fields need to edited by the db a support person.

We need to allow users to read only and allow the support staff only to make
changes to the db. Can we do this on the folder leverl or do we need to do
it in the db?

Maybe an additional table called comments should be added. Folks can
add to the comments and can read them but can't change them.

This is in addition to locking down the basic forms for the 200 users.
Locking fields on a form in Microsoft Access
http://www.granite.ab.ca/access/locking_fields_on_a_form.htm
You can control who has the controls unlocked by putting those userids
into a table. And then using API: Get Login name
http://www.mvps.org/access/api/api0008.htm to validate the userid.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[Tony Toews [MVP]]

First, I notice that you have a split database format which is good, but from
your post it is not clear if each user has their own front-end on their own
machine. If this is not the case, but all means, you need to have each user
have their own copy of the front-end file on their workstation.

See the free Auto FE Updater utility see http://www.autofeupdater.com
to keep the FE on each PC up to date.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/