We're having touble with a DLL we've created in VB. When I built it I set it up to accept the database connection from the VB project that was calling it. This was working, but the DLL was unstable. My boss then went in and changed the way we declare the DLL to an Object rather than an instance of the Class. Now when we try to open an ADO recordset in the DLL using the connection it fails. My boss then decided to try opening a seperate connection in the DLL to the database, this worked for the ADO recordset, but now our combos that are linked to recordsets don't fill properly.

I know it's pretty vague, but that is a summary and anyone that could help with ideas I can always elborate if you need it and show you some code if that would help too.

You can pass database connections to DLLs right? And can someone give me the proper way to declare and call a DLL...it might all be stemming from that.