Ms Access Error 7787
to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 7 of 7 Thread: Error 7787 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 04-28-09,12:02 #1 lxf View Profile View Forum Posts Registered User Join Date Nov 2002 Posts 8 Unanswered: Error 7787 When encounter "Write Conflict" (Error 7787) in MS access, we get three buttons in the popup: [Save Record] [Copy To Clipboard], [Drop Changes] I want to trap this error in Form Error event, it seems Response = acDataErrContinue in the code is the same as click on [Copy to Clipboard]. How to write a code for the same as selecting the [Drop Changes] botton? Thank you. Reply With Quote 04-28-09,17:50 #2 Sinndho View Profile View Forum Posts Moderator Join Date Mar 2009 Posts 5,440 Provided Answers: 14 The Response parameter is used by MS Access to determine weather or not to display the default error message. I'm not sure which one is the most convenient but there are three values the Response parameter can have: Response = acDataErrDisplay Response = acDataErrContinue Response = acDataErrAdded Can't you simply trap the error and undo the changes? This kind of error is a real pain in the neck and one very difficult to manage. The best solution would be to identify why this error occurs (it should not in an usual situation) and fix the application accordingly. Unfortunately this is not an easy task. One of the most frequent cause for this error is when Access is used as a front-end and data are stored on a server (SQL Server for instance) and that this server uses triggers or user-defined functions that manupulate those data, like this: You change a value in Access --> This triggers a manipulation of the same data in the server --> Access considers that "someone else" tried to write the same data in the same time --> this generates a Write conflict error. One of the most vicious situa
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 19:23:51 GMT by s_wx1206 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a https://www.experts-exchange.com/questions/28071257/Access-2010-Write-Conflicts-and-Explicit-VBA-Save-Errors.html Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Access 2010: Write Conflicts and Explicit VBA Save Errors Want to Advertise Here? Solved Access 2010: Write Conflicts and Explicit VBA Save Errors ms access Posted on 2013-03-20 MS Access Visual Basic Classic 1 Verified Solution 16 Comments 2,154 Views Last Modified: 2013-03-26 Hi everyone, While testing, I am getting odd errors thrown from subs with explicit save code, after I get the 7787 error that's trapped in Form_Error. It seems like I'm getting the last error that was thrown (for anything), but sometimes it ms access error seems like it could be a legitimate error. (I guess I wondering if the Me.Undo or the Me.Refresh in Form_Error could cause another error to be thrown). A decompile/recompile seems to fix it -- so I'm guessing that I've forgotten to close the form sometimes while I've been working with the code -- causing some scrambling. My question is: should I ever be getting an error in the procedure that saves (like cmdSave_Click) after the Jet error is thrown? (Optimistic locking) Here's the typical Form_Error Code: Private Sub Form_Error(DataErr As Integer, Response As Integer) On Error GoTo HandleErr 'MsgBox "DataErr = " & DataErr Select Case DataErr Case gERR_JETWRITECONFLICT_7787 gMsgWriteConflictErr_Undo With Me .Undo .Refresh End With Response = acDataErrContinue Select all Open in new window And here's some typical Save code: Private Sub cmdSave_Click() On Error GoTo HandleErr If Me.Dirty Then Me.Dirty = False End If ExitHere: Exit Sub HandleErr: 'MsgBox "cmdSave Error# " & Err.Number Select Case Err.Number Case gERR_RECORD_DELETED '3167