To restrict operations on recordsets, you really should set up MS. Access security. This is soewhat 'painful' and you need to read the directions carefully and proceed with extreme caution (inital set up ONLY on an isolated machine with a backup copy of everything at each step ... )
Once you have this set up, assing each user to the group(s) they need to be in for various operations (Read Only; Modify; Delete; Add). You can even have groups which will ahve different 'permissions' for different tables. (You COULD extend this to specific fields, but I have never seen this actually done).
Once the security groups are set up and users are assigned to the appropiate groups, You need to code each operation to check the user's group and permissions before allowing the operation.
This is a non trivial operation, but it does include the benefit of providing complete control over the operations on the data set and the mechanisim to generate a transaction log of all operations - which can include the User's name, date/time stamp and the machine Id. If you need the protection of user security, this is a good way to go.
MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over