Hi John
No problems. Best to ask and be clear.
When it happens its at a random time and record, but interestingly the record that is affected can then be replicated on another machine.
I have not tried using filters to find the record and see if the issue is resolved.
There is a relationship of the problem to the number of records and volume of information per record as I have found that by splitting the table into smaller chunks (currently 2) the problem goes away for a while till we start adding a lot more records.
The tables contain information that cannot be normalised. Memory issue perhaps and related to the way we are find the record?
The code we are using is as follows:
Dim sTD_ID As String
Dim rs As DAO.Recordset
Set rs = Me.RecordsetClone
sTD_ID = Str(Nz(Me![cboID], 0))
rs.FindFirst "[ClientId]=" & Str(Nz(Me![cboID], 0))
If rs.NoMatch Then
MsgBox "Sorry, no such record '" & Str(Nz(Me![cboID], 0)) & "' was found.", _
vbOKOnly + vbInformation
Me.Combo5.SetFocus
Me.Combo5.Value = ""
Else
Me.Recordset.Bookmark = rs.Bookmark
If ClientId = 0 Or Str(Me.TD_ID) <> sTD_ID Then
MsgBox "WARNING - record not found or incorrect client record may be displayed"
Me.cboID.SetFocus
Me.cboID.Value = ""
ElseIf IsNull(DateCalled) Then
DateCalled.SetFocus
Else
MsgBox "Date already exists - please check"
Me.SetFocus
Me.cboID.Value = ""
End If
End If
rs.Close
Set rs = Nothing
Cheers
Mike