Is is possible to only allow user enter data through form

[Ming]

I want a database only allow user to enter data through form, they might can
read the related tables, but they can't write anything directly through those
tables, is that possilbe?
I have tried those permission setting, but once the accese of the table is
denied, the related form can't be used, either.

 

[John W. Vinson]

I want a database only allow user to enter data through form, they might can
read the related tables, but they can't write anything directly through those
tables, is that possilbe?
I have tried those permission setting, but once the accese of the table is
denied, the related form can't be used, either.

I don't understand.

You want the user to be able to enter data, but not to be able to enter data
into the tables?

Where do you want the data entered TO? Data is stored only in tables, not in
Forms!

Do you want the user to be able to enter only NEW records and not edit
existing ones, or what?

 

[BruceM]

I read this question to ask whether users can be prevented from entering
data directly into tables, and be required to enter data into the table only
by way of the bound form.
To the OP, my best guess about your question is that when users open the
database they see what is called the database window, with tabs for Tables,
Queries, Forms, etc. As it stands they are selecting the table itself
rather than the form. The way to prevent that is not to give them the
option. Go to Tools > Startup and make your data entry form the Startup
form. There are various Startup options to prevent the use of special keys,
prevent the use of the shift bypass key, and so forth. You have to decide
the level of restriction. For instance, you could decide to allow users to
use F11 to open the database window.
*Be sure to make a copy before you make the changes, or you could lock
yourself out*
There are usually ways to get around being locked out, but why give yourself
the hassle?
If the users need to use several forms or reports you could add buttons to
your Startup form to let you open other forms or reports. You could also
use a separate switchboard as the Startup form. You could create the
Switchboard either by way of the Switchboard Manager or by creating your
own Startup form, with buttons to navigate through your database.
Since I am guessing a bit as to the exact meaning of your question, I will
not try to add any more detail just now.

 

[Albert D. Kallal]

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

 

[John W. Vinson]

I read this question to ask whether users can be prevented from entering
data directly into tables, and be required to enter data into the table only
by way of the bound form.

<d'oh!>

Thanks Bruce, on rereading that's exactly the issue. I need more sleep.

 

[Ming]

John, thank you for your quick response, sorry I didn't make my question clear.
BruceM, that exactly what I asked, I just follow what you said and build a
separated menu form, it works now, thanks.
Albert, thank you for your example.

So, as long as user don't know the "Shift" or "F11" key, the database is
secure. Otherwise I have to write some additional code to disable the special
key, correct?