Does modify level give the user delete capability? 2

[kat25]

Good day,
I have 2 questions. I hope you can help me.
Question 1:
I have a database that I have just completed building. I have not secured the database or done a split. My users will need to "insert" data into an existing record and will need to "add" data to an existing record. They will also need to "create" a new record. I do not understand how to define their security level in ACCESS terms in order to ensure they can perform these function but not have the capability to delete a record. Does "modify" give the user delete rights?

Question 2:
Is there any function that will "hide" the listing of my tables in the database window?

Thank you kindly for your help.
kat

 

[ssecca]

Not sure what version of access you are using , but

Question 1) Modify has to do with develpment rights not record change, delete, add rights. Go to the security option and select the users and group option select the tables tab and then you can set the delete read add ect. options per user as you wish

Question 2) much easier. Right click on the table you want to hide while in the database window select properties and then select &quot;hidden&quot;. Now close the properties window and go to <Tools><options> on the tool bar and de-select hidden objects from the view tab. Everything marked as hidden goes away like magic.

Good luck
ssecca

 

[kat25]

I am using Access 2000.
I will give this a try.
Thank you for your prompt reply.

 

[MichaelRed]

for records, the attribute is &quot;edit&quot;, and -while it does not permit &quot;delete&quot; in the absoloute sense, it does allow the editing of a record to any extent, which may render the record sufficiently unlike the original that it becomes 'deleted' for all pratical purposes.



MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[kat25]

If my users require the edit capability, is there any method of me securing the data in my tables?

kat

 

[MichaelRed]

hmmmmmmmmmmmm,

either not really or it depends.


If you can (more or less) prevent users from accessing the table data directly, you can set he controls attributes (locked) according to your needs to protect the data. Add some extensive V&V code to make sure the edits are appropiate to the user / record / field, etc and provide an audit trail of who changed what (and at least when) and you can at least track 'who done it'. It is a fair amount of work / effort, but then if it is worth doing, you might as well do it right?

For A version of an audit trail see faq181-291.




MichaelRed
m.red@att.net

Searching for employment in all the wrong places