Only allow users to input data in to tables through forms

[Guest]

I have an access databases where users are supposed to input data through
forms. However, someone is opening the table and directly tampering with the
data.

Is there a way to prevent this?

 

['69 Camaro]

Hi, Vick.

Is there a way to prevent this?

Yes. Implement User-Level Security and only assign permissions to the
tables to the database owner. As the database owner, create queries with
the "WITH OWNER OPTION" clause (also known as "Run With Owner Permissions"
(RWOP)). Create forms bound to these queries and give the Group that the
users are members of permission to only open/run the forms and reports, no
other objects.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Hi, Vick.

For more information on implementing User-Level Security, please see the
following Web page for the Security FAQ:

http://support.microsoft.com/?id=207793

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Joan Wild]

Yes. Implement User-Level Security and only assign permissions to the
tables to the database owner. As the database owner, create queries with
the "WITH OWNER OPTION" clause (also known as "Run With Owner Permissions"
(RWOP)). Create forms bound to these queries and give the Group that the
users are members of permission to only open/run the forms and reports, no
other objects.

Well, except for the RWOP query. Users will also need at least Read Data
permission on the query.

 

[Joan Wild]

If you don't want to implement security, there are a number of things you
can do that may be sufficient for your purposes:

Backup your database; you can easily lock yourself out playing around with
these features.

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not include the
Windows, Unhide item)
uncheck the allow special keys (this will disable the F11 key, among
others)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to
forms, reports and modules (If you do this, be certain to keep your original
mdb in case you need to make changes).

 

['69 Camaro]

Hi, Joan.

Thanks. And I forgot to mention the Open/Run database permission is
required, too.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.