Results 1 to 4 of 4
  1. #1
    BrightSoftware is offline Advanced Beginner
    Windows 7 32bit Access 2010 32bit
    Join Date
    Jun 2016
    Posts
    45

    Error 7787

    Sometimes we get the error 7787 (Record changed bij another user).
    There is only 1 user in the database.
    How can we solve this?

  2. #2
    isladogs's Avatar
    isladogs is offline MVP / VIP
    Windows 10 Access 2010 32bit
    Join Date
    Jan 2014
    Location
    Somerset, UK
    Posts
    5,954
    Not enough info to help you.
    Identify exactly what you were doing when it occurs.
    Colin, Access MVP, Website, email
    The more I learn, the more I know I don't know. When I don't know, I keep quiet!
    If I don't know that I don't know, I don't know whether to answer

  3. #3
    Micron is offline Virtually Inert Person
    Windows 10 Access 2016
    Join Date
    Jun 2014
    Location
    Ontario, Canada
    Posts
    12,737
    You'd have to post the relevant code - assuming there is any. Likely more than one event is involved.
    Or step through it line by line and see if you can spot the problem. Often it's because you've made some modification to a bound field then made a change elsewhere yet the first change hasn't been saved. To Access it looks like 2 users are changing data at the same time (it can't tell that it's the same person). The record level locking property can also come into play here. The 2 changes might be on separate records, but if record level locking is set to be a large set of records, it's not that the same record is being edited, but the same page (or section) of records.

    In summary, try stepping through your code with the above in mind.
    The more we hear silence, the more we begin to think about our value in this universe.
    Paraphrase of Professor Brian Cox.

  4. #4
    davegri's Avatar
    davegri is offline Excess Access
    Windows 10 Access 2016
    Join Date
    May 2012
    Location
    Denver
    Posts
    3,389
    I've run into this under these conditions:
    A form is open and some event causes an SQL update to the underlying bound table.
    Then an event wants to open another form that involves the same table. The new form opens and triggers the error.

    The solution is to clear the record status in the first form before opening the new form.
    Code:
    If me.dirty then me.dirty = false

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 1
    Last Post: 09-22-2016, 05:05 AM
  2. Replies: 1
    Last Post: 07-26-2016, 06:34 AM
  3. Replies: 6
    Last Post: 03-17-2016, 02:10 PM
  4. Replies: 3
    Last Post: 01-23-2014, 07:49 AM
  5. Replies: 0
    Last Post: 07-16-2012, 05:42 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums