Dll Question[Resolved Thanks]

[OUSoonerFan]

I have an calling a procedure in a dll. The app creates an SQL connection to a database. Can I pass the Connection itself also to the procedure? I am trying to get away from having to go through the whole connection thing again on the dll. So in the class module of the dll can I have it say something like

Public Sub PullRecords(sSQLCommand as string, sSQLConnection as SQLConnection)

Also...
What would be the best way of doing this. I have 2 private classes in the main public class of the dll. I am going to call a procedure in the public which will then call it one of the private classes depending on what is sent. This dll loads only when I open a new window in main app. for every window open i want it to launch a seperate instance of that dll. and then use the functions in the dll anytime needed as long as the window has not been close. Is that a good way of doing it or should I just have it call to the dll when ever needed and have the connection to the database created each time something is called on dll. (Which is why i asked the first question).

Basically all the dll is doing is taking from one database and placing values into another one and vice versa.

Thanks in advance.