Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Message: Another User edited this record....

Status
Not open for further replies.

Chrisbi

Technical User
Nov 27, 2002
26
US
All of a sudden I'm getting this message when I try to save record changes a second time from a particular form:

"Another user edited this record & saved the changes before you attempted to save your changes; re-edit the record."

I am the only user---database is only on one computer for now but I will be distributing to other users. Have I inadvertedly changed some setting... If so, is this an issue I should be addressing when I set up for multiple users (will use backend on server; front end on desktop)....
 
Hi Chrisbi,

Sounds like you might be running some sort of update query.

If you are, put this at the beginning of your code:

On Error Resume Next

Put this after the query:

DoCmd.RunCommand acCmdSaveRecord

Otherwise I don't know what to suggest.

Bill
 
1. You have the Record Locks property set to No Locks. You should change it to Edited Record (in all your forms). This change will remove that dialog, but instead you'll get a trappable run-time error, as only one user will be able to edit a record at a time.

2. You start editing the record (either manually or by code)

3. You attempt to change data by a(nother) code snippet before saving the first edit.

You are the only user, but you're acting as two.

I slightly disagree with Bill, as I'd put
DoCmd.RunCommand acCmdSaveRecord
before running the query (or the second edit attempt)

But saving the record when you're done editing is definitely the way to go.

HTH


[pipe]
Daniel Vlas
Systems Consultant

 
Thanks for suggestions but I'm still not sure... my form is unbound so I save using docmd.runsql & sql statement. I append the record to the table first with some basic info from another form/table & then give the user a screen/form to add additional info. I don't get the message when I append the record (from Form1) or the first time I change data & save (Form2). But I get the message if I then make a change to another field (Form2).... Once I click on message I just continue editing, etc. & saves are all OK. I just worry that I've coded something or checked off some property that I hadn't realized.....
 
Hi Chrisbi,

Have you actually tried danvlas' and my suggestion.

Without seeing your code it isn't possible to say whether there is a coding problem. If the above doesn't suppress the message, please post your code and SQL.

Bill
 
I am getting a similar popup message, when editing data in my app. The app FE is on workstation with the BE on a server. App is secured with user account and ID, no password. Currently only 1 user is running the app. When entering and editing data, she gets the following message: "Write COnflict: this record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user user made. Copying the changes to the clipboard, etc.....". The options are "Save the record", "Copy to the Clipboard" and "Drop changes".
"Default record locking" is set to "No Locks" and "Open database using record level locking" is checked.
The app is in shared mode, and there are no other users at this time.
Thank you for helping.
 
Also have this problem.

Tried above suggestions with no success.

Tracked it down to a memo field in a record that returns #Error when queried.

Tried update query to make it "". Same message.

Tried exporting table, importing table, make table up to the record, repair, compact and a whole lot more.

Only thing I can do is delete record which client does'nt want as it is an invoice and autonumbered.

Still stumped.

 
I had a similar problem with the memo field and could not resolve it. So I added a menu item to the menu bar (command button would also work) that allowed the user to "fix" the record by calling a function that duplicated the bad record (setting memo field to "") and then deleted the bad record.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top