Checking if an Delete using ADO in a DLL was ok.

[henkep]

Hi i have written an Dll for a project that takes care of all the database activity. I open the connection in the Class Initialize and use the same connection object for all methods in the DLL.
Some of the methods return a disconnected recordset and some of the methods should just return True or false. Now to the problem I can´t get the hang of how I check that the Boolen set if I for example deletes a record. I have tried to use withevents on the connection object but I cant get it to work. If I have 3 methods accessing a equipment table in the db.
1 . InsertEQ
2. UpdateEQ
3 . DeleteEQ

All the actions should return booleans but the ExecuteCompleted method just checks the connection object not the individual methods, it would be good to have som error handeling also.
Any ideas on how to do this..?

/Henrik

[axion_sa]

Return enumerations

' Declarations.
Public Enum ReturnTypeConstants
  rtOk = 0
  rtFail = 1
  rtError = 2
End Enum
 
Public Function InsertEQ(Blah Blah Blah) As ReturnTypeConstants
    Dim enReturn As ReturnTypeConstants
 
    On Error Goto InsertEQ_Error
 
    enReturn = rtFail ' Fails until success.
    ' Your code....
 
    enReturn = rtOk
 
 
InsertEQ_Error:
    If Err.Number <> 0 Then
        MsgBox Err.Number & " - " & Err.Description
        Err.Clear
        enReturn = rtError
    End If
 
    ' Return.
    InsertEQ = enReturn
End Function

[henkep]

Greate, thanx alot..

One more question , if I expect a ADODB.Recordset back but something goes wrong. How can I tell the reciver that it went to the woods...

/Henrik

[axion_sa]

In the procedure that does the returning, if anything goes "to the woods" set the recordset to Nothing & return it. At the client:

Set myRs = Proc()
If myRs Is Nothing Then
    MsgBox "It's all gone pear shaped."
Else
    ' Your processing goes here.
End If

[techgnome]

Also, if there was an error during the execution of the SQL, the connection object has an Errors collection in it that will have the list of the error(s) that happened. By checking the Errors.Count you can tell if the SQL when tits up or not.

[henkep]

But the connection object lies in the DLL , how do I access that.

/H

[henkep]

More questions..

I have a Store Procedure that returns Multiple recordsets but when I try to pass them back I just get One of them and the error code:
"Current provider does not support returning multiple recordsets from a singel execution"

Is there a way of resolving this?

/Henrik