here's an example of the code in the DLL:
--------------------------------------------
Function DoIt(rst as Variant) as String

Dim strSQL as String
Dim SQLConn as ADODB.Connection

strSQL="select username, userid from accounts"
OpenConnection SQLConn

rst=GetRecords(strSQL, SQLConn)

CloseConnection SQLConn

'error handling feature goes here.... it works though

End Function
---------------------------------------------

The OpenConnection, CloseConnection, and GetRecords are custom made functions that I use frequently and I KNOW there is no problem regarding those.

The ASP looks like:
----------------------------------------------
dim obj, rst, errors
set obj=Server.CreateObject("MyDLL.IDB")
set rst=Server.CreateObject("ADODB.Recordset")
errors=obj.DoIt(rst)
if not (errors "")
redirect to error page
else
response.write ""
rst.MoveFirst()
While not rst.EOF do
response.write ""
response.write rst("username")
response.write ""
response.write rst("userid")
response.write ""
loop
response.write "
end if
---------------------------------------------

That's pretty much all that happens. I know that the SQL statement DOES return records, and that the DLL is registered locally.... I do this twice in the page. the first time it works, but when I add the 2nd Function call (a different function) the page errors out on the line: "rst.MoveFirst()" (I bolded it too) with the error - Operation cannot be performed while the object is closed....

I'm running out of ideas on what to do here, so if anyone knows, I'd appreciate the help.

-Rob

First a warning. You probably know more about ADO than I do. It's been a year or so since I've used it (wish I had my trusty ADO book but its at work) That said:

So you're saying that in previous cases, you've been able to enumerate through the recordset AFTER its corresponding connection has been closed?

I've always thought that a recordset created from a connection is normally a live object and that closing the connection also closes the recordset. I've always closed the connection AFTER I was done with the recordset. I know you can have a client-side recordset (with RDS I think) but I'm not sure how that works. Or maybe changing the cursor type not to use server-side cursors (if thats even relevant).