MS Access Multiuser - How to share db

Author

How to share db

spacerocket

2005-08-23, 3:24 am

How do I enable sharing of a db I just created?

I created all usernames in a workgrp file and put it in a shared network
folder accessible (R/W) by all. However, when one user opens the db, a temp
file is created and it locks the db. Other users cannot open the file at all.

I checked in all the users' PCs, all of us have Access default db open set
to shared and not exclusive. What else could be causing the problem? Thanks
in advance.

TomU

2005-08-23, 7:25 am

First, you should split the application into a data back-end and an
application front-end. (See Help on Split Database. There's a wizard in
Access that makes it pretty easy.) Place the backend on the server and
install the front-end on each user's PC.

Second, give all users full rights to the folder containing the database
backend (read, write, create, delete). When a user in a multi-user app opens
a database on the server, it must create the .ldb file on the server so that
others can share the database. If the user doesn't have rights to create and
delete in that server folder then the .ldb is created on their local hard
drive and prevents others from opening the database.

---
Tom Unkefer

"spacerocket" wrote:

> How do I enable sharing of a db I just created?
>
> I created all usernames in a workgrp file and put it in a shared network
> folder accessible (R/W) by all. However, when one user opens the db, a temp
> file is created and it locks the db. Other users cannot open the file at all.
>
> I checked in all the users' PCs, all of us have Access default db open set
> to shared and not exclusive. What else could be causing the problem? Thanks
> in advance.

Joan Wild

2005-08-23, 11:25 am

TomU wrote:
> First, you should split the application into a data back-end and an
> application front-end. (See Help on Split Database. There's a
> wizard in Access that makes it pretty easy.)

Do not use the Database Splitter wizard on a secured database; that will
remove all security on the backend. Instead split it manually. See
www.jmwild.com/SplitSecure.htm

> Second, give all users full rights to the folder containing the
> database backend (read, write, create, delete). When a user in a
> multi-user app opens a database on the server, it must create the
> .ldb file on the server so that others can share the database. If
> the user doesn't have rights to create and delete in that server
> folder then the .ldb is created on their local hard drive and
> prevents others from opening the database.

Also ensure that you don't give the mdw and the mdb the same name. They
each need to be able to create a ldb.

--
Joan Wild
Microsoft Access MVP

spacerocket

2005-08-28, 3:23 am

Thanks. I managed to share the database now. I have another question. I
created a Security workgroup for all users in the company. Is it possible to
use the same workgroup for all my databases or do I need to create a new
workgroup for each database?

Thanks again.

"TomU" wrote:
[color=darkred]
> First, you should split the application into a data back-end and an
> application front-end. (See Help on Split Database. There's a wizard in
> Access that makes it pretty easy.) Place the backend on the server and
> install the front-end on each user's PC.
>
> Second, give all users full rights to the folder containing the database
> backend (read, write, create, delete). When a user in a multi-user app opens
> a database on the server, it must create the .ldb file on the server so that
> others can share the database. If the user doesn't have rights to create and
> delete in that server folder then the .ldb is created on their local hard
> drive and prevents others from opening the database.
>
> ---
> Tom Unkefer
>
>
> "spacerocket" wrote:
>

Joan Wild

2005-08-28, 11:24 am

You can use the one mdw for all your databases.

--
Joan Wild
Microsoft Access MVP

spacerocket wrote:[color=darkred
]
> Thanks. I managed to share the database now. I have another question.
> I created a Security workgroup for all users in the company. Is it
> possible to use the same workgroup for all my databases or do I need
> to create a new workgroup for each database?
>
> Thanks again.
>
> "TomU" wrote:
>

Sponsored Links