Hello all!
Is there a way to lock down a table to prevent any additions? I want to still be able to edit it, but not add any new records.

I know you can do this on a form, but I need to apply this to the actual table.

Any ideas?



Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!

__________________
Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!

If you are using Access as a front and back end, go to tools, security. Setup user groups and users and set permissions for each table you have. I hope this helps.

Actually, I was wanting to avoid using that method. I tried once before and had too many issues with our engineers setting a database password instead of their users password. If there is a way to fight what I'm doing, they'll try it!

Any other ideas

(I appreciate your suggestion!)

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!

What you do is in your form's design view, set these properties:

Allow Edits: Yes
Allow Deletions: No
Allow Additions: No
Data Entry: No


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

Add a field to the table, numeric byte or integer as required, indexed unique. Enter a sequential numeric integer in each field. Then place a validation rule on the new field in the table design mode:

>0 And <10

and users will be limited to 9 entries in the table. If users can get into design mode of the table you can build your front end application as an mde with a hidden table (you may want to prefix the table name with 'usys' or 'msys' so it is ordinarily hidden, place the range constraints in this table in the front end table and create a relationship to your linked (or local) data table that you wish constrained, enforce referential integrity and turn off cascade updates.

If users can get at the database design or you permit them to view tables, they should be accountable for the design.

Ciao
Jürgen Welz
Edmonton AB Canada
[email protected]

can you use SQL Server or MSDE? I do not like Access security at all. It comes with too many anoyances.



Sal

I agree with you on not liking Access security, but unfortunatly, my knowledge is limited to it. I have no experience in SQL Server, or linking Access to any other application or storing it on a server. I don't actually work for an IS/IT department, I'm actually in our Document Control department. Access is something that I picked up on my own by experimenting with it and now everyone else here expects me to do all the databases since we do not have anyone else who knows VB or VBA. I do not mind at all that they depend on me...it actually makes me feel more appreciated. But it just makes it hard when I can't figure something out on my own because I hate to keep bothering all of you.
Any ways, I was able to take the easy way out on this one. I feel dumb for not thinking of it before posting my question for help. Since the database was split, I just re-named the table and issued it back out to the users. (I had to re-issue it out either way.) Then I was able to lock down the table through the forms design and still let them view it. Since they get their part as an .mde, they can't get around it. It was actually Greg's post that made me think of doing that.

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!