But the function UpdCheck is in the Update Trigger code for the table. What it is supposed to do it prevent any updates on rows that have an assoc_id > 5000 (those rows are "secured"). The update code I enter in the command window:

   update timeusernew set user_name="blahblah" ;
   where assoc_id > 3000

would normally be done within a form, and the user that is making the update will not necessarily know about the protected data rule stored in the DBC, which is also keeping the user from changing anything with a value over 5000. If I change the command window code to:

   update timeusernew set user_name="blahblah" ;
   where assoc_id > 3000 and assoc_id < 5000

then what I'm doing is putting the security logic on the end-user side of things, which I am trying to avoid.

There has got to be some way to quickly do this, I am pretty sure my logic is off in my UpdCheck function....