Good day all,

	We currently have a data base on a shared drive, and it has the main 
table on A SQL server , The problem that when a multiple users tries to 
use it messages that the data base was locked by another user
So pls. , can any one help me in solving this problem



Best regards,

Ahmed Khamis
Vodafone Egypt
Customer operation
Mob:  xxx-xxx-xxxx
Ext:56-1107
Ahmed.khamis@v...

On Wed, 31 Jul 2002 17:54:33 +0200 "Ahmed Khamis" wrote:

> 	We currently have a data base on a shared drive, and it has the main 
> table on A SQL server , The problem that when a multiple users tries
> to use it messages that the data base was locked by another user
> So pls. , can any one help me in solving this problem

This one has been asked, answered and argued about countless  
times on this list.  You must use the database splitter to make a 
front end/ back end arrangement. The front end will  have 
everything in it except tables. It will link to the tables in the back 
end and in the SQL server. The back end stays on the shared 
drive. You convert the front end to an mde file and have each 
user place a copy on their computers' hard drives. I the users 
already have Access on their computers, just copy the front end 
mde file to their hard drives. If not, get a copy of Office (nn) 
Developer edition with the package and deploy wizard, and use 
it to make an installation package with Access RunTime.

Paul

Just an added note. You don't necessarily have to convert the Front End 
database into an mde. It can remain an mdb but it should be local to the 
client machines as Paul has told you.

Amy

> On Wed, 31 Jul 2002 17:54:33 +0200 "Ahmed Khamis" wrote:

> 	We currently have a data base on a shared drive, and it has the 
main 
> table on A SQL server , The problem that when a multiple users tries
> to use it messages that the data base was locked by another user
> So pls. , can any one help me in solving this problem

This one has been asked, answered and argued about countless  
times on this list.  You must use the database splitter to make a 
front end/ back end arrangement. The front end will  have 
everything in it except tables. It will link to the tables in the back 
end and in the SQL server. The back end stays on the shared 
drive. You convert the front end to an mde file and have each 
user place a copy on their computers' hard drives. I the users 
already have Access on their computers, just copy the front end 
mde file to their hard drives. If not, get a copy of Office (nn) 
Developer edition with the package and deploy wizard, and use 
it to make an installation package with Access RunTime.

Paul

I don't think you need the database splitter if ALL of the data is on SQL
Server.

If ALL of the data is on SQL Server, you just need to give your users local
copies of the MDE.

However, if there is ANY data stored in the MDE _that you need to be shared_
then you will need to split your MDE so that the shared data can reside on
the shared MDE an the forms can be local to each user as Paul described.
Some local data may not be shared - for example, in one of my apps I have a
local table that lists the names of the linked tables.  This table is never
updated (except during coding) so it is not shared data, and every user has
a copy of it in their MDE on their machine.  All the real data is kept in
SQL Server.




-----Original Message-----
From: PStreeter@C...
[mailto:PStreeter@C...]
Sent: Wednesday, July 31, 2002 2:11 PM
To: Access
Subject: [access] Re: A locked chared data base


On Wed, 31 Jul 2002 17:54:33 +0200 "Ahmed Khamis" wrote:

> 	We currently have a data base on a shared drive, and it has the main

> table on A SQL server , The problem that when a multiple users tries
> to use it messages that the data base was locked by another user
> So pls. , can any one help me in solving this problem

This one has been asked, answered and argued about countless  
times on this list.  You must use the database splitter to make a 
front end/ back end arrangement. The front end will  have 
everything in it except tables. It will link to the tables in the back 
end and in the SQL server. The back end stays on the shared 
drive. You convert the front end to an mde file and have each 
user place a copy on their computers' hard drives. I the users 
already have Access on their computers, just copy the front end 
mde file to their hard drives. If not, get a copy of Office (nn) 
Developer edition with the package and deploy wizard, and use 
it to make an installation package with Access RunTime.

Paul