HELP! PLEASE

[Daniel Kaseman]

Will someone (an expert) please help me figure out how to prevent the
following error from occuring:

"Couldn't Update; Currently Locked"

This error displays when i click on the plus sign on the table record, to
display the Subdatasheet.

I noticed that if there are several users entering data into the table that
the subdatasheet is linked to, that the error occurs then.

I proved it. I asked 2 of the users of our 5 user team to exit out of that
particular table, and then I went back to my computer to click on the plus
sign, and the subdatasheet appeared normally, no error message.

All 5 of us are entering data into the same table that has the same
subdatasheets, and each one of us may occasionally get the error if more
than one person is entering data into THAT table.

But isn't MS Access supposed to allow more than one user to enter data into
the same table at the same time?

I thought the above error should only occur when 1 user is modifying the
data of 1 field in1 record, while at the same time another user is modifying
the same data of the same field of the same record.

But this activity is NOT what we are doing. We are all entering data into
different records, but in the same table.

Thank you for your assistance,
Daniel

 

[Guest]

/* soapbox rant mode on
1. Subdatasheets are EVIL and should be avoided at all costs.

2. Allowing users to directly enter data into a table is a really, really
bad idea. You should be using a proper form and subform combination. Further
the database should be split with the tables in the backend and the forms,
reports, ect., in the Front End. Each person should have their own copy of
the FE.
soapbox rant mode off */

Go to Tools, Options, Advanced tab. Makes sure that Default open mode is set
to Shared; Default record locking is Edited record; and Open database using
record-level locking is selected.

Also make sure that all users have read, write, create, and delete
privileges to the folder holding the database mdb file. Not just the file
itself; rather the entire folder.

 

[Danny J. Lesandrini]

Jerry:

I'm not familiar with the "subdatasheets are evil" camp and though I haven't
used them much, when I have, they were the perfect solution.

For example, I just implemented a solution with these requirements:

a) Need to show records in datasheet view
b) Users cannot edit datasheet, but double click to open edit form
c) Edits performed on unbound form that writes new record, preserving
the existing record as an audit trail with the new record linked to it's
progenitor via a ParentID
d) User interface should allow users to view audit history, if desired.

Subdatasheets are perfect for this. The Datasheet shows the most recent
version of the record and the subdatasheet shows all related (by ParentID)
records that are NOT the most current. None of them are editable inline,
but double-clicking on the Datasheet (but not the subdatasheet) opens the
unbound edit form where we strictly control what gets changed and how.

For a different client, they had a view they wished to display for primary
table records (tblProposals) in datasheet view, where editing was allowed.
The subdatasheet provided a simple way for them to enter and edit child
records in the tblProposalDistributor table. Clean, simple and I've seen no
issues, even in a replication environment.

So, I guess I'm wondering why anyone is down on subdatasheets and if
there is a reason, I'd better know now, before I start using these things all
over the place.

 

[Guest]

Besides my silly rant, did the rest of my post help with your problem?

 

[Nick Coe \(UK\)]

If you go into Access Help and search on Record Locking
you'll get a lot of info about row level and page level
locking, and No Locks, Edited Record and All Records.

In general from A2K onwards you can get row level locking by
setting Row Level (or Record Level) Locking and Edited
Record. This is sometimes called fine granularity
pessimistic locking - sounds like an indigestion medecine
<g>.

Bear in mind that if you use a bound form or subform then
Access will automatically take care of the locking process.
If you edit a table directly then you could run into
trouble.

The options for locking are in Tools|Options|Advanced and
will need to be set on EVERY machine accessing that
database.

Also make sure none of your users are starting to edit a
record then pausing part way through and doing something
else. That record can stay locked until they complete the
edit.

If your application is not split into a front end
(application on each workstation) and back end (data file
shared on server) do so _now_.

--
Nick Coe (UK)
http://www.alphacos.co.uk/ AccHelp + pAnimal
http://www.mrcomputersltd.com/ Repairs Upgrades

In Daniel Kaseman typed:

 

[Danny J. Lesandrini]

Jerry, I didn't say it was a silly rant, and your advice for not editing
directly in tables is a must. In fact, I forgot to mention that my use
of subdatasheets was done with a Form/Subform displayed in
datasheet mode, NOT directly with tables. That is, of course, how
I'm able to control things like double-clicking a record to bring up
the edit form.

I am curious if people have found undesireable issues with the
subdatasheets.

 

[warrior]

Hi Danny,
Do you have the form automatically opening on startup?

I have had problems with this in the past with a multi user
application.

If you do, you may want to remove it from your database utilities start
up and replace it with a macro.