I am very, very new to using this software, but have an immediate need to 
break through a roadblock on a project we have underway.  In a nutshell, we 
have a database with roughly 15 input fields designed to track the activities 
of a group of roughly 50 employees.  We are having major frustrations, 
probably due to ignorance, with data input as multiple users attempt to 
access the data form simultaneously.  The database quickly converts to 
read-only when more than one user accesses it.  We are still working in MS 
Access 2003, hoping to upgrade later this year.  Is the data access page the 
solution to this issue?  Any advice is greatly appreciated.

First, split the database. There is a wizard if you have no experience with 
the very easy manual process. Put a copy of the front-end on each 
workstation, linked to the data (tables) on a server in the back-end. Make 
sure that the Access is open (as well as the database) for shared access, 
and start the options with no locks. All users need read, write create, and 
delete permissions on the server folder which holds the back-end.
-- 
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"bankingbuddy" <bankingbuddy@discussions.microsoft.com> wrote in message 
news:31DECEAA-0833-4F01-B977-D82C33825179@microsoft.com...
>I am very, very new to using this software, but have an immediate need to
> break through a roadblock on a project we have underway.  In a nutshell, 
> we
> have a database with roughly 15 input fields designed to track the 
> activities
> of a group of roughly 50 employees.  We are having major frustrations,
> probably due to ignorance, with data input as multiple users attempt to
> access the data form simultaneously.  The database quickly converts to
> read-only when more than one user accesses it.  We are still working in MS
> Access 2003, hoping to upgrade later this year.  Is the data access page 
> the
> solution to this issue?  Any advice is greatly appreciated. 

See this article:

    Implementing a Successful Multiuser Access/JET Application
    http://www.accessmvp.com/TWickerath/articles/multiuser.htm

Follow all of the steps, including disabling Name Autocorrect, splitting the 
database, establishing a persistent connection, etc. You'll likely want to 
look into using the AutoFE Updater utility to help ease the burden of 
distributing updates to your application.

> Is the data access page the solution to this issue?

I would not consider DAPs to be a solution. For one thing, they were 
deprecated in Access 2007. You can still open them in A2007, but you cannot 
make design changes to DAPs in A2007. And, they have been completely removed 
from Access 2010, which is currently in beta release.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

"bankingbuddy" wrote:

> I am very, very new to using this software, but have an immediate need to 
> break through a roadblock on a project we have underway.  In a nutshell, we 
> have a database with roughly 15 input fields designed to track the activities 
> of a group of roughly 50 employees.  We are having major frustrations, 
> probably due to ignorance, with data input as multiple users attempt to 
> access the data form simultaneously.  The database quickly converts to 
> read-only when more than one user accesses it.  We are still working in MS 
> Access 2003, hoping to upgrade later this year.  Is the data access page the 
> solution to this issue?  Any advice is greatly appreciated.