Nikolay DMITRIEV
asked on
MS Access single form simultaneous memo field edit by several users
Dear experts,
MS Access 2003 database: individual front-ends, common back-end;
Two users are trying to edit same memo field of same record in single form from individual FEs.
Program is producing #Error with nothing I can do with this field later...
Question 1: Is it possible to restore this field? At least, to open this Memo field for editing again (if the info inside can not be recovered...most probably not)
Question 2: What is correct way to resolve such conflicts? (some indication maybe, some mdal...etc.)
Thanks in advance,
MS Access 2003 database: individual front-ends, common back-end;
Two users are trying to edit same memo field of same record in single form from individual FEs.
Program is producing #Error with nothing I can do with this field later...
Question 1: Is it possible to restore this field? At least, to open this Memo field for editing again (if the info inside can not be recovered...most probably not)
Question 2: What is correct way to resolve such conflicts? (some indication maybe, some mdal...etc.)
Thanks in advance,
ASKER
Good day Jim,
Thanks for support.
1. I've got #Error in the table as well.
2. Compact & Repairs does not help.
Moreover, I can not handle memo field anymore, i.e. I have to delete complete record and create the new one ..
See attached snapshot of what I get putting subject memo field on focus...
3. Thanks for the hint: I've adjusted Form Design>Data>Record Lock>Edited record.
Will ask guys to simulate their previous actions
Capture.JPG
Thanks for support.
1. I've got #Error in the table as well.
2. Compact & Repairs does not help.
Moreover, I can not handle memo field anymore, i.e. I have to delete complete record and create the new one ..
See attached snapshot of what I get putting subject memo field on focus...
3. Thanks for the hint: I've adjusted Form Design>Data>Record Lock>Edited record.
Will ask guys to simulate their previous actions
Capture.JPG
Seems like a pointer got messed up.
I don't think however this was caused by more than one user being in there at one time per say. As I said, locking is always in play no matter what the settings are.
More likely, this was caused by a network interruption or someone doing a Ctrl/Alt/Del and end task when they could not get anywhere.
Jim.
I don't think however this was caused by more than one user being in there at one time per say. As I said, locking is always in play no matter what the settings are.
More likely, this was caused by a network interruption or someone doing a Ctrl/Alt/Del and end task when they could not get anywhere.
Jim.
ASKER
Good day Jim,
I have feedback from the guys.
Actually, your proposal with "edited record" worked well.
They could not get #Error despite various actions.
There is only one matter to close the issue definitely.
After modification, second user simply can not modify the memo field. Without any visible reasons.
Question:
I need indication that the record is currently edited by another user.
Do you think its possible to implement, actually, whatsoever: unbound txt field saying OnCurrent that "record is currently edited by another user", or change of color of any control etc.
Something like:
If record is locked then
txt[text1].Visible=True
Thanks in advance and apologies for additional burden
I have feedback from the guys.
Actually, your proposal with "edited record" worked well.
They could not get #Error despite various actions.
There is only one matter to close the issue definitely.
After modification, second user simply can not modify the memo field. Without any visible reasons.
Question:
I need indication that the record is currently edited by another user.
Do you think its possible to implement, actually, whatsoever: unbound txt field saying OnCurrent that "record is currently edited by another user", or change of color of any control etc.
Something like:
If record is locked then
txt[text1].Visible=True
Thanks in advance and apologies for additional burden
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot Jim.
Will start playing with above without delay.
Have a nice week-end
Will start playing with above without delay.
Have a nice week-end
ASKER
Thanks for support.
1. Open the back end and table directly. See if you can see the field data or not. You probably won't be able to.
2. Make a copy and then do a compact and repair. You may be able to edit the record, and might get some of the field data (that however is doubtful)
On question 2, the short answer is, it should not happen. Locking does occur no matter who's working on what. Memo fields are odd though in that they are not stored with the rest of the record, so it's possible for users to be on the same LVP (Long Value Page) even if they are not on the same record.
Still, I don't understand how two users caused what happened.
Only change I would make is to change the forms Record Locks to Edited Record, meaning the record will be locked as soon as the first user starts to edit the record.
Jim.