Thanks for the info Marex! I was scrolling thru old posts & found this 1 by JHausmann:

1) create a "lock" table that has 1 entry
2) when you want to write to the DB, the program attempts to lock the sole record. If it cannot, someone else is using the database-if the program CAN lock the record-proceed with your work.

Dr_Evil is this what you were talking about? What I'm trying to do is make sure that when an Admin is updating/building a test NO ONE can get ANYTHING from that table til he's done. Would using adLockPessimistic for the recordset ensure that? Also when I have a User saving his test results to a table(by Inserting the info as new records) I don't want ANY other User to be able to save their results UNTIL the 1st one is done-will adLockPessimistic solve this as well? I apologize for the confusion but I can't find ANYWHERE on MSDN the specifics of how to prevent multiple users from adding to a table in DB at once! Thanks for ANY help!