By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,197 Members | 1,151 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,197 IT Pros & Developers. It's quick & easy.

MS Access 2000 > file locked by another user

P: n/a
Hello,

I set up a database a few months ago and placed it on our company
network. In the beginning, there was no problem opening it, even when
someone else was working in it at that time.

The last fourteen days we encounter an error message: 'file locked by
another user'. I don't seem to recall that I made changes to the
database since let's say Dec 10, 2004.

It is supposed to work for everybody at all time. The database is set
to 'shared'.

What is the problem and how can I fix it?

Thanks for you reply,

Lieve
Nov 13 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
go*******@hotmail.com (Lieve) wrote:
The last fourteen days we encounter an error message: 'file locked by
another user'. I don't seem to recall that I made changes to the
database since let's say Dec 10, 2004.

It is supposed to work for everybody at all time. The database is set
to 'shared'.

What is the problem and how can I fix it?


Hi Lieve.

It's likely to have locked up because of using a single file in a multi-
user environment. You should really split the database and provide each
user with their own 'front end'.

A 'front end' is an mdb file which contains all objects *except* the
tables, a 'back end' is *just* the tables. You would normally have the BE
on a server in a public location and each user would have their own locally
held FE which would be linked to the BE.

Search the help for 'split database' for more info.

HTH - Keith.
www.keithwilby.com
Nov 13 '05 #2

P: n/a
Keith, can you explain more about putting front ends for each user?
Why would you not just split the database and put a shortcut to the one
front end that is created, at each users end?

I ask because I am finishing up a project in the next couple of weeks
and I do plan to research splitting the db for best practices.
Any advice would be appreciated.

Nov 13 '05 #3

P: n/a
"misscrf" <mi*****@yahoo.com> wrote:
Keith, can you explain more about putting front ends for each user?
Why would you not just split the database and put a shortcut to the one
front end that is created, at each users end?

I ask because I am finishing up a project in the next couple of weeks
and I do plan to research splitting the db for best practices.
Any advice would be appreciated.


It is best practice to provide each user with their own FE. Some people
disagree with this and provide only one common FE but I would advise
against this since there is a danger of data corruption. A dedicated FE
also has a performance benefit.

There are a few different methods for providing users with a FE. I find
the simplest solution (assuming all users are on the same network) is to
use a batch file. The users' shortcut would point to the batch file which
would, in turn, copy the FE from a 'public' (read-only) folder to a
prescribed area on their local drive and then open it.

Typically, the batch file code might look something like this:

ECHO OFF
XCOPY "X:\MyPath\Public\MyGUI.mdb" C:\Temp\MyFolder /I
START "MyGUI" /MAX "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"C:\Temp\MyFolder\MyGUI.mdb" /wrkgrp "X:\MyPath\Public\MyWrkGrp.mdw"

Of course, this assumes that C:\Temp\MyFolder exists but you can ensure it
does by sending all users a hyperlink to another batch file which prepares
their C drive accordingly.

HTH - Keith.
www.keithwilby.com
Nov 13 '05 #4

P: n/a
Why is all of that code needed? I thought that you use the wizard to
split up the db. Why the code for giving each user their own front end?
Can't you just copy it out?

misscrf

It is never too late to become what you could have been ~ George Eliot

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #5

P: n/a
please no spam <pl**********@myworld.com> wrote:
Why is all of that code needed?
*All* that code?
I thought that you use the wizard to
split up the db.
Yes, you can do that, but the code copies the FE as described in my earlier
post. It doesn't do anything in terms of the 'splitting' process, it merely
makes the FE available on the local drive.
Why the code for giving each user their own front end?
Can't you just copy it out?


Yes, you can copy it manually if you wish.
Nov 13 '05 #6

P: n/a
Thanks. I just get scared when I see code. Where does it go? How does
it run? lol

Anyway, I will only have 2-4 users using this app, so I am not worried
about manually copying the frontend out...

misscrf

It is never too late to become what you could have been ~ George Eliot

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #7

P: n/a
"please no spam" <pl**********@myworld.com> wrote
Anyway, I will only have 2-4 users using this app


Not if your db is useful. The Database Corollary to Moore's Law says that
your number of users will double with every feature you add.
Darryl Kerkeslager
Nov 13 '05 #8

P: n/a
Well, I hope that after a while of testing I might be able to sell it (
after a lotttt of testing) but it really is for our hr department to
just enter and report on candidates who apply for jobs. There are only
2-4 people that do that work.
lol

misscrf

It is never too late to become what you could have been ~ George Eliot

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.