Problem 1:

I've put the back-end of my database on a folder on the server, also in that
folder is the security database (workgroup). When i 'am working on 1
workstation it works perfectly but when another one wants to login it gives a
fault, admin is already in use. The other workstation got the acces to the
folder but has 1 restriction they may not delete any documents.

Problem 2:

When the other workstation is working alone on the database, he has no
authority to any table, query or what ever! But i've given the person the
rights to work with te tables etc. I think it's because i did'n't make the
workstation a member of the workgroup, but i can't test it right now.

Who can help me!!!

You must provide read/write permissions for the folder for all users who
need to access the database. User will also have to have delete rights as
well, I'd assume - they'll have to be able to delete the "locking" file (the
..ldb file) generated by Access. This may also be what's causing your #2
problem ... check the backend directory with all user logged out of the db
.... if you find an .ldb file in the directory, delete it ... Access will
recreate it as needed.

--
Scott McDaniel
InfoTrakker Software
"Richard" <(E-Mail Removed)> wrote in message
news:5AA80E7B-41A1-4FBA-A4AA-(E-Mail Removed)...
> Problem 1:
>
> I've put the back-end of my database on a folder on the server, also in
> that
> folder is the security database (workgroup). When i 'am working on 1
> workstation it works perfectly but when another one wants to login it
> gives a
> fault, admin is already in use. The other workstation got the acces to the
> folder but has 1 restriction they may not delete any documents.
>
> Problem 2:
>
> When the other workstation is working alone on the database, he has no
> authority to any table, query or what ever! But i've given the person the
> rights to work with te tables etc. I think it's because i did'n't make the
> workstation a member of the workgroup, but i can't test it right now.
>
> Who can help me!!!

Richard:

Were you able to solve your Problem #1? I also continue to have the same
problem, even after I have given the users read/write/delete permissions on
the folder. Any help would be appreciated. Thanks.
--
Julie


"Richard" wrote:

> Problem 1:
>
> I've put the back-end of my database on a folder on the server, also in that
> folder is the security database (workgroup). When i 'am working on 1
> workstation it works perfectly but when another one wants to login it gives a
> fault, admin is already in use. The other workstation got the acces to the
> folder but has 1 restriction they may not delete any documents.
>
> Problem 2:
>
> When the other workstation is working alone on the database, he has no
> authority to any table, query or what ever! But i've given the person the
> rights to work with te tables etc. I think it's because i did'n't make the
> workstation a member of the workgroup, but i can't test it right now.
>
> Who can help me!!!

Also, they need create permission on the folder. Also ensure you don't give
the same name to both the mdb and mdw.

--
Joan Wild
Microsoft Access MVP

Julie wrote:
> Richard:
>
> Were you able to solve your Problem #1? I also continue to have the
> same problem, even after I have given the users read/write/delete
> permissions on the folder. Any help would be appreciated. Thanks.
> --
> Julie
>
>
> "Richard" wrote:
>
>> Problem 1:
>>
>> I've put the back-end of my database on a folder on the server, also
>> in that folder is the security database (workgroup). When i 'am
>> working on 1 workstation it works perfectly but when another one
>> wants to login it gives a fault, admin is already in use. The other
>> workstation got the acces to the folder but has 1 restriction they
>> may not delete any documents.
>>
>> Problem 2:
>>
>> When the other workstation is working alone on the database, he has
>> no authority to any table, query or what ever! But i've given the
>> person the rights to work with te tables etc. I think it's because i
>> did'n't make the workstation a member of the workgroup, but i can't
>> test it right now.
>>
>> Who can help me!!!

Joan:

Appreciate your response. Actually "create" and "delete" are not choices on
our server. There is "modify" and "full control." I have given users "full
control" on the folders containing both the back-end (tables) and the
workgroup file. They are not in the same folder and are not named the same.
I have given users a "front-end" (queries, forms, reports, etc.) on their own
hard drive. Security works like I intend. The secured database only opens
from the shortcut.....Everything works wonderfully, except for this little
problem. When I have the database open on my computer, with my username (in
the Admins group), other users get this error message: "Could not use
'Admin'; file already in use."

Here's why I think the problems is with my computer:
1. When I log onto the database on my computer with a different user name,
then another user tries to log onto the database on their computer, they get
the error message.
2. When two other users log onto the database on their own computers with
their usernames, both are able to open it.
3. When I log onto the database on a different computer with my username,
then another user tries to log onto their computer, they are sucessful.
4. It is also interesting that if another user logs onto the database on
their computer before I do, then I log onto the database on my computer, we
are both able to use it.
I have talked to our IT guy about reinstalling Office XP. (Access had been
doing some other silly things even before I started getting into security.)
He seems reluctant to do that. I think it's worth a try.

Do you have any other ideas? Thanks for all your help. I'm finally
"getting it!"

--
Julie


"Joan Wild" wrote:

> Also, they need create permission on the folder. Also ensure you don't give
> the same name to both the mdb and mdw.
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Julie wrote:
> > Richard:
> >
> > Were you able to solve your Problem #1? I also continue to have the
> > same problem, even after I have given the users read/write/delete
> > permissions on the folder. Any help would be appreciated. Thanks.
> > --
> > Julie
> >
> >
> > "Richard" wrote:
> >
> >> Problem 1:
> >>
> >> I've put the back-end of my database on a folder on the server, also
> >> in that folder is the security database (workgroup). When i 'am
> >> working on 1 workstation it works perfectly but when another one
> >> wants to login it gives a fault, admin is already in use. The other
> >> workstation got the acces to the folder but has 1 restriction they
> >> may not delete any documents.
> >>
> >> Problem 2:
> >>
> >> When the other workstation is working alone on the database, he has
> >> no authority to any table, query or what ever! But i've given the
> >> person the rights to work with te tables etc. I think it's because i
> >> did'n't make the workstation a member of the workgroup, but i can't
> >> test it right now.
> >>
> >> Who can help me!!!
>
>
>

That message "could not use 'admin'; file already in use" suggests to me
that at some point the backend may have been closed inappropriately.

With everyone out of the database, verify that there is no ldb file in
either of the folders where the backend or workgroup file are. If you see a
ldb file delete it. I would then open the backend and compact it.


--
Joan Wild
Microsoft Access MVP

Julie wrote:
> Joan:
>
> Appreciate your response. Actually "create" and "delete" are not
> choices on our server. There is "modify" and "full control." I have
> given users "full control" on the folders containing both the
> back-end (tables) and the workgroup file. They are not in the same
> folder and are not named the same. I have given users a "front-end"
> (queries, forms, reports, etc.) on their own hard drive. Security
> works like I intend. The secured database only opens from the
> shortcut.....Everything works wonderfully, except for this little
> problem. When I have the database open on my computer, with my
> username (in the Admins group), other users get this error message:
> "Could not use 'Admin'; file already in use."

Joan:
No .ldb files in either folder. Should I still compact the back-end?
--
Julie


"Joan Wild" wrote:

> That message "could not use 'admin'; file already in use" suggests to me
> that at some point the backend may have been closed inappropriately.
>
> With everyone out of the database, verify that there is no ldb file in
> either of the folders where the backend or workgroup file are. If you see a
> ldb file delete it. I would then open the backend and compact it.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Julie wrote:
> > Joan:
> >
> > Appreciate your response. Actually "create" and "delete" are not
> > choices on our server. There is "modify" and "full control." I have
> > given users "full control" on the folders containing both the
> > back-end (tables) and the workgroup file. They are not in the same
> > folder and are not named the same. I have given users a "front-end"
> > (queries, forms, reports, etc.) on their own hard drive. Security
> > works like I intend. The secured database only opens from the
> > shortcut.....Everything works wonderfully, except for this little
> > problem. When I have the database open on my computer, with my
> > username (in the Admins group), other users get this error message:
> > "Could not use 'Admin'; file already in use."
>
>
>

Yes, you should routinely compact the backend anyway.

However the message you are getting with 'Admin' in it is referring to the
default Admin user. Normally that user does not have any permissions in a
secured mdb. So perhaps someone is getting in using their default
system.mdw??


--
Joan Wild
Microsoft Access MVP

Julie wrote:
> Joan:
> No .ldb files in either folder. Should I still compact the back-end?
> --
> Julie
>
>
> "Joan Wild" wrote:
>
>> That message "could not use 'admin'; file already in use" suggests
>> to me that at some point the backend may have been closed
>> inappropriately.
>>
>> With everyone out of the database, verify that there is no ldb file
>> in either of the folders where the backend or workgroup file are.
>> If you see a ldb file delete it. I would then open the backend and
>> compact it.
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Julie wrote:
>>> Joan:
>>>
>>> Appreciate your response. Actually "create" and "delete" are not
>>> choices on our server. There is "modify" and "full control." I
>>> have given users "full control" on the folders containing both the
>>> back-end (tables) and the workgroup file. They are not in the same
>>> folder and are not named the same. I have given users a "front-end"
>>> (queries, forms, reports, etc.) on their own hard drive. Security
>>> works like I intend. The secured database only opens from the
>>> shortcut.....Everything works wonderfully, except for this little
>>> problem. When I have the database open on my computer, with my
>>> username (in the Admins group), other users get this error message:
>>> "Could not use 'Admin'; file already in use."

Joan:

Compacting the back-end fixed it! YIPPPPEEEE! Thank you, thank you, thank
you.
--
Julie


"Richard" wrote:

> Problem 1:
>
> I've put the back-end of my database on a folder on the server, also in that
> folder is the security database (workgroup). When i 'am working on 1
> workstation it works perfectly but when another one wants to login it gives a
> fault, admin is already in use. The other workstation got the acces to the
> folder but has 1 restriction they may not delete any documents.
>
> Problem 2:
>
> When the other workstation is working alone on the database, he has no
> authority to any table, query or what ever! But i've given the person the
> rights to work with te tables etc. I think it's because i did'n't make the
> workstation a member of the workgroup, but i can't test it right now.
>
> Who can help me!!!