"C. Sharp" wrote:

> We use our database in a Citrix environment and it always shows user ADMIN as
> the current user.  However, whenever more than one person tries to access it
> at the same time to up date data we get one of two errors:
>
> "Placed in a state of Lock by user ADMIN" (something similar to this) and
> that user cannot even open the database.
> -or-
> "You do not have exclusive access to the database at this time.  If you
> proceed to make changes, you may not be able to save them later."  This
> allows us to make changes but we are never sure they are saved until we
> double check.
>
> Any ideas on how to make this quit happening.  I am a newbie at DB security
> so please explain in terms an idiot could understand!
>

"Joan Wild" wrote:

> Access always uses security (even for databases you haven't secured).  It
> uses a workgroup file called system.mdw and silently logs you in as a user
> named Admin.  That is why you see that username - everyone is 'Admin'.
>
> Users need read/write/create/delete permission on the folder where the mdb
> is located.  Users also need exclusive access on a mdb in order to make
> design changes.
>
> You should split your database into frontend/backend and give each user a
> copy of the frontend to use.
>
> Even in a Citrix environment, users should have their own copy of the FE.
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
> "C. Sharp" wrote:
>
> > We use our database in a Citrix environment and it always shows user ADMIN as
> > the current user.  However, whenever more than one person tries to access it
> > at the same time to up date data we get one of two errors:
> >
> > "Placed in a state of Lock by user ADMIN" (something similar to this) and
> > that user cannot even open the database.
> > -or-
> > "You do not have exclusive access to the database at this time.  If you
> > proceed to make changes, you may not be able to save them later."  This
> > allows us to make changes but we are never sure they are saved until we
> > double check.
> >
> > Any ideas on how to make this quit happening.  I am a newbie at DB security
> > so please explain in terms an idiot could understand!
> >

> C. Sharp
> I'm not familiar with the concept front/back end.  Is there someplace
> I can go to read about it so I will know how to do this.  The entire
> DB resides on Citrix and we login using Windows Terminal
> Services/Citrix ICA client. Thanks!
>
> "Joan Wild" wrote:
>
>> Access always uses security (even for databases you haven't
>> secured).  It uses a workgroup file called system.mdw and silently
>> logs you in as a user named Admin.  That is why you see that
>> username - everyone is 'Admin'.
>>
>> Users need read/write/create/delete permission on the folder where
>> the mdb is located.  Users also need exclusive access on a mdb in
>> order to make design changes.
>>
>> You should split your database into frontend/backend and give each
>> user a copy of the frontend to use.
>>
>> Even in a Citrix environment, users should have their own copy of
>> the FE.
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>>
>> "C. Sharp" wrote:
>>
>>> We use our database in a Citrix environment and it always shows
>>> user ADMIN as the current user.  However, whenever more than one
>>> person tries to access it at the same time to up date data we get
>>> one of two errors:
>>>
>>> "Placed in a state of Lock by user ADMIN" (something similar to
>>> this) and that user cannot even open the database.
>>> -or-
>>> "You do not have exclusive access to the database at this time.  If
>>> you proceed to make changes, you may not be able to save them
>>> later."  This allows us to make changes but we are never sure they
>>> are saved until we double check.
>>>
>>> Any ideas on how to make this quit happening.  I am a newbie at DB
>>> security so please explain in terms an idiot could understand!