469,962 Members | 2,299 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,962 developers. It's quick & easy.

A97 does not prevent entry of new records from a form bound to a table

MLH
I have a form frmEditAdminData.

Its AllowAdditions property is set to No. I thought this meant
the form could not be opened in a manner that allowed the
appending of new records to its source table. But that is
untrue. I open the form from code this way:

DoCmd.OpenForm "frmEditAdminData", , , , acFormEdit

How can I prevent the addition of records to the source
table of a form in Access 97?
Nov 13 '05 #1
2 1320
MLH wrote:
I have a form frmEditAdminData.

Its AllowAdditions property is set to No. I thought this meant
the form could not be opened in a manner that allowed the
appending of new records to its source table. But that is
untrue. I open the form from code this way:

DoCmd.OpenForm "frmEditAdminData", , , , acFormEdit

How can I prevent the addition of records to the source
table of a form in Access 97?


You do this (as the developer of the app) by NOT putting the acFormEdit argument
into the OpenForm statement. There are several ways to override the default
AllowAdditions property setting. You have discovered one of them.

If you want to give an MDB file to others and let them make design changes to it
then there is nothing you can do to prevent edits to a table. If you give them
an MDE and/or implement User Level Security then you have some control over who
can do what.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2
MLH
<snip>
A very neat an succinct point. Thxvery much.
You do this (as the developer of the app) by NOT putting the acFormEdit argument
into the OpenForm statement. There are several ways to override the default
AllowAdditions property setting. You have discovered one of them.

If you want to give an MDB file to others and let them make design changes to it
then there is nothing you can do to prevent edits to a table. If you give them
an MDE and/or implement User Level Security then you have some control over who
can do what.


Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Iain Miller | last post: by
9 posts views Thread by Catherine Jo Morgan | last post: by
5 posts views Thread by Aspnot | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.