I can't post as it's a proprietary project and won't work if you had it any way. The access file is just a GUI for a SQL server app because IT won't let me have VS.
I'm using recordsetclone because the form recordset is not accessible when you are using a streaming recordset via ostream. This is the code used to create a streaming record set. What changes in the form, changes on the SQL server.
Code:
Public Function Clone(ByVal oRs As ADODB.Recordset, Optional ByVal LockType As ADODB.LockTypeEnum = adLockUnspecified) As ADODB.Recordset
If Not bDev Then On Error GoTo PROC_ERR
PushCallStack ("mdlFunctions - Clone")
Dim oStream As ADODB.Stream
Dim oRsClone As ADODB.Recordset
'save the recordset to the stream object
Set oStream = New ADODB.Stream
oRs.Save oStream
'and now open the stream object into a new recordset
Set oRsClone = New ADODB.Recordset
oRsClone.Open oStream, , , LockType
'return the cloned recordset
Set Clone = oRsClone
'release the reference
Set oRsClone = Nothing
PROC_EXIT:
PopCallStack
Exit Function
PROC_ERR:
GlobalErrHandler Err.Number, Err.Description, True, gCLATrackID, Erl
Resume PROC_EXIT
The original method was to use a stored procedure to delete the record in question. The procedure didn't fail, but when a different procedure that loads up the streaming recordset tried to run, it locked itself up even after trying to kill the connection and rekindle it.
I resorted to using the Access built in macros to delete and that's when I discover the last record issue above.