Could't Update; Currently Locked by Another Session on this Machine

There were two previous posts for this question back in Dec 2002 with no resolution.

This problem exists when using a MEMO field (also tested with OLE Object field and get the same error).  The senario is that data is entered into this MEMO field.  Later the field is edited and more data added.  This continues to work until the field has around 2k worth of characters at which time an attempt is made to save the record and then the error message "Could't Update; Currently Locked by Another Session on this Machine" appears.

One work around seems to be to add another record and then come back to this record and then you can get past the 2k limit.  But then the extra record needs to be deleted.
LVL 5
niblickAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jjafferrCommented:
Hi niblick,

I would recommend the following:
make this memo field (memo1) Unbound and it will be used for data entry,
make 2 Bound hidden memo fields,
On lost focus of the memo1, count the number of characters, and if more than 2k, then split them in both the hidden memo fields,
otherwise fill in the first hidden memo field.

On Current of the Form, make sure:
[memo1]=[memo2] & [memo3]

Hope this helps

Jaffer
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
flavoCommented:
2k??? Dont they hold 64k charaters???
0
niblickAuthor Commented:
flavo........yes, a memo field holds 64k characters.

jjafferr,
The field is already unbounded and I have tried to update using methods and recordsets.  I currently am not displaying the full contents of the field and only use the form field to append the data via an update to the existing data.  This has sparked an idea in my mind though, something about what was said in another thread.  Something about two forms being open.  I do not have the form opened twice but I do have the record open on two forms.   The initial display form and then the edit form.  Perhaps if I close the initial display form and reopen it after I have finished with the edit form then this might get around the locking problem.  Let me test it out and if it works I will give you the points for making me think to hard.  Ow, it hurts!
nib
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

niblickAuthor Commented:
Just a note so everyone knows why I have a display form and an 'edit' form.  The first form just displays the data.  Users cannot edit the data on this form.  The application is like a running journal where you can add comments but not edit what has already been entered.  Therefore, the second form is only used to add new comments to the existing comments field.
0
niblickAuthor Commented:
The problem seems to have been with having the other form still open and locking the record.  What I do now is close the current form before opening the 'edit' (add comments) form.  Then when I close this form I re-open the other form.

jjaffer, thanks for making me think.
0
jjafferrCommented:
Hey I have too many other ideas, I don't mind throwing some to get you think more and throw some points at me ;o)

Thanks for the points and the grade.

jaffer
0
ajg23Commented:
Dang, I have the same problem but do NOT want to close the original form (which has a list of notes from encounters). Really would love another workaround...
0
ajg23Commented:
I finally did the following workaround which I'm pretty happy with given the limitations of this Acess problem: I wound up writing a TRUNCATED version of the big memo field to the record in addition to the big memo field itself. Only the TRUNCATED version is in the query in the main list so it doesn't interfere with my EDIT form's ability to save! (The edit form saves a truncated version after the main version!)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.