Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / August 2005

Tip: Looking for answers? Try searching our database.

How to share db

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
spacerocket - 23 Aug 2005 03:28 GMT
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 - 23 Aug 2005 12:03 GMT
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

> How do I enable sharing of a db I just created?
>
[quoted text clipped - 5 lines]
> to shared and not exclusive. What else could be causing the problem? Thanks
> in advance.
Joan Wild - 23 Aug 2005 16:27 GMT
> 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
[quoted text clipped - 3 lines]
> 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.

Signature

Joan Wild
Microsoft Access MVP

spacerocket - 28 Aug 2005 05:01 GMT
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.

> 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
[quoted text clipped - 20 lines]
> > to shared and not exclusive. What else could be causing the problem? Thanks
> > in advance.
Joan Wild - 28 Aug 2005 16:55 GMT
You can use the one mdw for all your databases.

Signature

Joan Wild
Microsoft Access MVP

> 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
[quoted text clipped - 29 lines]
>>> open set to shared and not exclusive. What else could be causing
>>> the problem? Thanks in advance.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.