H
Hugster
Once a form is opened in the database other users are unable to open the
database. Hod do I compensate for this in access.
database. Hod do I compensate for this in access.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Arvin Meyer
Hugster said:Once a form is opened in the database other users are unable to open the
database. Hod do I compensate for this in access.
You need to split the database into a back-end (all the data tables) and a
front-end (everything else) and link the 2 using a network share that
everyone can see. There's a splitter wizard in Tools ... Database Utilities
that will walk you through it.
Put a copy of the front-end on each machine and make sure that Access is set
up in options not to open the file exclusively. Also make sure that each
user has permissions to delete and create files, or you won't be able to
create the record locking file (LDB)
It should work fine from there.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
T
Todd Shillam
If you have not split the database into two parts, a front-end and
back-end, that's where I would start. From your description of the problem,
it appears like your database is a single file that is saved in a network
folder and gets 'locked' whenever a person opens the file.
A Brief Explanation
The back-end is commonly kept (stored) in a network folder where each
intended user is given access to the folder (a network administrator can
help setup a share). Security is the concern here--you don't want people
getting access that don't need it.
The front-end is commonly installed on the client machines, your
computer. However, unlike the back-end, the front-end application has
'linked' tables to the back-end. You can use UNC or drive mapping to make
the connection to back-end tables.
TIP: Its good practice to save the front-end application in the same folder
on each computer--you'll thank me later. For example:
C:\Program Files\CompanyName\ApplicationName\ApplicationFile.mdb
If you have questions, keep'em coming.
Best regards,
Todd
Once a form is opened in the database other users are unable to open the
database. Hod do I compensate for this in access.
back-end, that's where I would start. From your description of the problem,
it appears like your database is a single file that is saved in a network
folder and gets 'locked' whenever a person opens the file.
A Brief Explanation
The back-end is commonly kept (stored) in a network folder where each
intended user is given access to the folder (a network administrator can
help setup a share). Security is the concern here--you don't want people
getting access that don't need it.
The front-end is commonly installed on the client machines, your
computer. However, unlike the back-end, the front-end application has
'linked' tables to the back-end. You can use UNC or drive mapping to make
the connection to back-end tables.
TIP: Its good practice to save the front-end application in the same folder
on each computer--you'll thank me later. For example:
C:\Program Files\CompanyName\ApplicationName\ApplicationFile.mdb
If you have questions, keep'em coming.
Best regards,
Todd
Once a form is opened in the database other users are unable to open the
database. Hod do I compensate for this in access.
L
Larry Daugherty
Hi,
Change from "Exclusive" to Shared" in Tools|Options|Advanced|Default Open
Mode
HTH
Change from "Exclusive" to Shared" in Tools|Options|Advanced|Default Open
Mode
HTH