Records evaporate - Why?

[revver]

I have a file server which is home to the back end db.

Each user has a copy of the front end and those copies live on a terminal server in this folder structure

[SharedUsers]

[User A]
[User B]
[User ...]
[User R]​

The application is used to record notes about client contact events.
eg "phoned client, told them the news... The reply was ..."

A situation just occurred where User A entered 4 new records, exited the front end and reopened it. She viewed the records (Numbered 21682-21685). She told user P to go read the records to update his knowledge of their mutual client. User P looks and reports that notes are not there.

User A verifies records are missing and calls me. I find that record 21680 is the most recent. While I watch, user A creates a dummy record. It is given record number 21682. 21681 is not in the list.

Where do I start looking to debug this? Any ideas welcome.

 

[jackd]

I'd start by looking at the code that actually saves the new records.
Why not post it so we can all see?

Have you tried a situation with a front end on the users PC?

 

[revver]

I have not tried a FE on a workstation. Very few of them have Access installed.
Here is the 'save' code.

Private Sub cmdSign_Click()
Dim Msg As String
On Error GoTo Err_cmdSign_Click
    DoEvents
    If Not chkOk2Save Then                 'if box not ticked
        MsgBox conMustTick, vbOKOnly, "Can't Save"
        Exit Sub
    End If
    If Me.Dirty Then Me.Dirty = False    'Save
    If cboRoleID > 0 And chkOk2Save Then 'the form probably has data so display msg
        Msg = "The note has been saved as  >> " & Me.txtNoteID & " <<." & vbCrLf
        Msg = Msg & "How does this compare with the number noted earlier." & vbCrLf
        Msg = Msg & "It should be higher by at least one." & vbCrLf & vbCrLf
        Msg = Msg & vbCrLf & "Now you can" & vbCrLf
        Msg = Msg & "   - enter another note" & vbCrLf & "   - or exit."
        MsgBox Msg
    Else
        DoCmd.Beep
    End If
    If Not Me.NewRecord Then RunCommand acCmdRecordsGoToNew
    
    chkOk2Save = False      'for next time, just in case the form has no data

Exit_cmdSign_Click:
    Exit Sub

Err_cmdSign_Click:
    If Err.Number = 3021 Then Exit Sub  ' No current record (chkOk2Save not ticked?)
    MsgBox Err.Description & " " & Err.Number
    Resume Exit_cmdSign_Click

End Sub

It is launched by clicking cmdSign button which is on a subform. The subform also contains all the fields for the record.

My debug efforts so far: When the form opens, the user is informed of the highest existing record number. The MsgBox in this save routine then advises the actual record number that was allocated. I have not ever received a report that the allocated number is <= highest RecNum. No surprise there.

The bewildering part is that all 4 records were there and correctly numbered for about the 15 minutes that it took User A to enter all 4. She checked all of them once she had finished entering them and all were correct and obviously retrievable. That's when she told User P to read them. Each record related to a different client.