"Could not lock file" - Access 2000,2002 and 2003 mixed?

Hello,

I have built a database system that is to be shared amongst a few people.
All was fine when we ran Access 2000 and 2002, but then one of the computers
was "upgraded". The new computer has access 2003, and now we get an error
when a second computer accesses the database. The error is "Could not lock
file". Is this a result of mixing the access versions? It can still be
opened by multiple users with access 2002, and I believe 2000 as well.

Thnx for any help.

Hi Uray,

Two possibilities come to mind:

1.) Has your new Access 2003 user set the default open mode to exclusive,
under Tools Options?

2.) Does this user have RWCD privileges for the shared folder on the file
server?
See the following KB article for more information:

Introduction to .ldb files
http://support.microsoft.com/?id=299373

The error is "Could not lock file". Is this a result of mixing the access versions?
No.

Tom
________________________________________

"uray" wrote:

Hello,

I have built a database system that is to be shared amongst a few people.
All was fine when we ran Access 2000 and 2002, but then one of the computers
was "upgraded". The new computer has access 2003, and now we get an error
when a second computer accesses the database. The error is "Could not lock
file". Is this a result of mixing the access versions? It can still be
opened by multiple users with access 2002, and I believe 2000 as well.

Thnx for any help.

Everything is set up properly in Access. I had forgot that the IT
department also had me move to a new server at the same time they gave us
the new computer. Checking it out today I discovered this server seems to
be the problem, not Access versions. The server is an Axis 100/IDE storage
server. I suspect it may have to do with the fact that the IT department
set it up for "Share" level access, not "User Level" access. I also
discovered that the server is completely unprotected, I was able to log in
and check it out myself :-) We do have full control (as does everybody
else) on the share, but I suspect it can't handle multi-user set up the way
it is.

I hate having to tell IT they (He) might have messed up. This new server is
also slooowww.... I'm not sure how long I can stand it. I had to turn off
"name tracking" to get the database usable again :-(

uray

I didn't change anything yet, won't do that until I have IT's OK.

"Tom Wickerath" AOS168 AT @comcast DOT net wrote in message
...
Hi Uray,

Two possibilities come to mind:

1.) Has your new Access 2003 user set the default open mode to exclusive,
under Tools Options?

2.) Does this user have RWCD privileges for the shared folder on the file
server?
See the following KB article for more information:

Introduction to .ldb files
http://support.microsoft.com/?id=299373

The error is "Could not lock file". Is this a result of mixing the
access versions?
No.

Tom
________________________________________

"uray" wrote:

Hello,

I have built a database system that is to be shared amongst a few people.
All was fine when we ran Access 2000 and 2002, but then one of the
computers
was "upgraded". The new computer has access 2003, and now we get an error
when a second computer accesses the database. The error is "Could not
lock
file". Is this a result of mixing the access versions? It can still be
opened by multiple users with access 2002, and I believe 2000 as well.

Thnx for any help.

Hi Uray,

Disabling Name Autocorrect is only one of the things that you should do to
help ensure a successful multi-user application. There are several other
items as well. Here is a list that I have started to compile:

1.) Make sure that Name Autocorrect is not activated.
http://support.microsoft.com/?id=290181

For additional reasons why you want to disable Name Autocorrect, see Allen
Browne's summary of reasons:

Failures caused by Name Auto-Correct
http://allenbrowne.com/bug-03.html

2.) Set the subdatasheet property for all tables to None.
http://support.microsoft.com/?id=275085

3.) Create relationships between the tables. This will cause Access to
automatically index all foreign keys (no need to index those fields
separately).

4.) Create indexes on any fields used in the criteria or sort rows (ie.
WHERE or ORDER BY clauses).

5.) Split the database into a front-end (FE) and back-end (BE) databases.
The FE contains all queries, forms, reports, macros, modules, and any local
tables (data that is relatively stagnant, such as a list of states, or user
preferences that are stored in a table). The BE contains only tables with the
shared data. A copy of the FE is loaded onto each user's PC. The BE is placed
on the file server.

6.) Open a persistent recordset from each FE as each user opens the
database. This recordset remains open during the duration of each user's
session. This can save a tremendous amount of time when opening queries,
forms and reports, since Access will use an available connection instead of
creating a new one each time.

http://support.microsoft.com/?id=889588
(See the section a little past halfway, titled "Optimize the Access or Jet
database engine-based database routines and methods").

7.) Make sure that the path to the back-end database is as short as
possible. In addition, none of the folder names should exceed 8 characters.

http://support.microsoft.com/?id=889588

8.) Make sure that each user's workstation has the same service packs
installed for Access, the JET database engine, and the operating system.

http://support.microsoft.com/kb/303528/

9.) Periodically compact the BE database on the file server. You can set
the FE database to "Compact on Close" as an option under Tools Options.

10.) It is a good idea to help your users clear out all temporary files
from their workstations, and run a disk defragment operation. If the user's
temporary folder is relatively full, this can really slow Access down.

http://support.microsoft.com/kb/288631/


Tom
_______________________________________

"uray" wrote:

Everything is set up properly in Access. I had forgot that the IT
department also had me move to a new server at the same time they gave us the
new computer. Checking it out today I discovered this server seems to be the
problem, not Access versions. The server is an Axis 100/IDE storage server.
I suspect it may have to do with the fact that the IT department set it up
for "Share" level access, not "User Level" access. I also discovered that
the server is completely unprotected, I was able to log in and check it out
myself :-) We do have full control (as does everybody
else) on the share, but I suspect it can't handle multi-user set up the way
it is.

I hate having to tell IT they (He) might have messed up. This new server is
also slooowww.... I'm not sure how long I can stand it. I had to turn off
"name tracking" to get the database usable again :-(

uray

I didn't change anything yet, won't do that until I have IT's OK.
_______________________________________

"Tom Wickerath" AOS168 AT @comcast DOT net wrote in message
...

Hi Uray,

Two possibilities come to mind:

1.) Has your new Access 2003 user set the default open mode to exclusive,
under Tools Options?

2.) Does this user have RWCD privileges for the shared folder on the file
server?
See the following KB article for more information:

Introduction to .ldb files
http://support.microsoft.com/?id=299373

The error is "Could not lock file". Is this a result of mixing the access versions?
No.

Tom
________________________________________

"uray" wrote:

Hello,

I have built a database system that is to be shared amongst a few people.
All was fine when we ran Access 2000 and 2002, but then one of the computers
was "upgraded". The new computer has access 2003, and now we get an error
when a second computer accesses the database. The error is "Could not lock
file". Is this a result of mixing the access versions? It can still be
opened by multiple users with access 2002, and I believe 2000 as well.

Thnx for any help.