Funny thing happened with a new db that my colleague just created. He set up users/groups such that developers can do everything, and regular users can only do open/run.
He logged as a regular user and got a "you can't open in exclusive mode..." error.
He asked me what it meant since he didn't open it exclusive. I suggested trying to do the Open -> select the db -> choose "Run" from the drop down. (This would have opened it in shared mode) -- and it worked! From now on he doesn't have a problem when logging in as a regular user.
My question is, did my forcing it to open in shared mode remove any remembrance of previously being opened exclusive?
I told him to to do 'Tools ==> Options ==> Advanced ==> Default Open mode = Shared' and he said that was already the way it was setup.
Any ideas what happened?
Thanks,
Jerry
Jerry Scannell
Jerry Scannell
He logged as a regular user and got a "you can't open in exclusive mode..." error.
He asked me what it meant since he didn't open it exclusive. I suggested trying to do the Open -> select the db -> choose "Run" from the drop down. (This would have opened it in shared mode) -- and it worked! From now on he doesn't have a problem when logging in as a regular user.
My question is, did my forcing it to open in shared mode remove any remembrance of previously being opened exclusive?
I told him to to do 'Tools ==> Options ==> Advanced ==> Default Open mode = Shared' and he said that was already the way it was setup.
Any ideas what happened?
Thanks,
Jerry
Jerry Scannell
Jerry Scannell