Record locked - Cannot update

W

Wazza

Hi
One of our clients has raised the above stating that the error "Record
Locked" occurs several times a day in a rather small database that is being
used.
The database has 5 users using a front end, and a single back-end that is
being updated. This is set by linked tables. The front-end is on a network
drive as is the back-end and all users have read/write access to the network
drive.

The problem seems to be occurring with one very particular person. Anytime
this person uses the database, it locks for everyone, however, if he is not
in the office, it seems the database does not lock. The front-end portion
that he uses has been "tested" on several machines, and the same thing
happens constantly.

We have created a "copy" of another users' front-end database and customized
to the problem customer, however, this has made absolutely no difference at
all.

It does seem to be down to a particular query that involves a listbox and
two text fields, where if the list box selection is made, the fields should
update with relevant data. I cannot say if this is always the case
though...as I only saw this Record Locked error once when selecting the field
and have pretty much only heard of all the other times (anything up to 20 a
day)

The database is about 10 - 15 Mb in size.
Maximum 5 users at any one time.
Record level locking enabled.
Open as shared database.

Any ideas from anyone would be really helpful. I did not design the
database, nor am I proficient in Access development, so not entirely sure
where to start.

Many thanks
 
G

Golfinray

The folder on the network drive where the BE resides also has to allow reads,
writes, and so forth. There also has to be space on that folder for Access to
make temp files and its locking file. That may not be the problem, but check
that first. Also make sure under tools/options that no locks are set.
 
W

Wazza

Thanks for that. Read/Write network folder access is available both in the
area where the back-end is stored as well as the area where the front-end is
stored (all users front-ends are in the same location - we were "testing")

I did some research on the "locking", and it seems access will use page
level locking if the default record level is not selected. Apparently, this
is worse? The absolute worst thing about the whole problem is that we copied
a database that we knew never locked and customized the switchboard and name
to be that of the person who seems to be causing the locks...and it still
locks (regardless of what PC he uses)

I've checked all of his network access (groups/folders and so on) and it's
identical to his colleague who happens to be the one who mentioned that the
database worked fine when this particular customer was not in the office.

I can't see this as a network or client PC issue, which is why I posted in
the access area. It's the last viable option, but I don't know enough about
it so have checked but a few things.

I can say that there has not been any manual coding in the database at all
so I've nothing awesome to offer the great devs here. There are queries used
by subforms and the controls are very simply labelled. There doesn't seem to
be any click event expressions or manual coding so in essence the database
has been put together by basically dragging things into place, and a few
queries/reports.

I don't know how the front-end and back-end setup is meant to be of any
great benefit since I just can't grasp why a database would be separated this
way, one so small? A much larger one, and I would think performance would be
the reason.

The actual error: Record locked - cannot update.

I expect I may need to line them up next to each other and watch them like a
hawk until it does the record locked? Just maybe.

I do hope someone can give me a clue. Thanks for your post though. Useful
information.
 
W

Wazza

Was just wondering...

If a form is locked, is it specific to the access front-end application on a
particular desktop i.e. will it need to be changed on all desktop front-ends
sharing the database? Or is it a case of change in a single place?

We've only a handful of people using it, so it's not like it would be hard
work or anything. But seeing as we've already copied a front-end we thought
was working, and the same happens because of the same person, I don't quite
know which way to look next...

Absolutely any input valued.

thanks
 
W

Wazza

Can exclusive database opening affect records in this way? Sorry for the
"question upon question" approach. Have to get out the "for dummies" book...

If a database is opened once as exclusive, will the same database always be
opened as exclusive if on the same machine?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top