starting ADO projects (VB6)

[tsd_man]

I've been strating out/experimenting with ADO connectiviity to a database (access97 db).
I want to create a project that has

(1) a client app.
(2) activeX DLL which handles the connections to the above db (open/close etc)
(3) another activeX DLL which handles the sql commands to the above db (SELECT etc)
(4) the access db itself


now does this mean that I can set up references in the following way

a) setup references to the ADO objects lib etc and only use ADODB recordset references in the client app
b) setup references to the ADO objects from each of the DLLs lib etc and use objects re: ADODB references where applicable


is there any problems with the above ?

[faisalkm]

if u use the dlls to open and close your db and to return data from the db, then you actually dont need any reffernce to ado objects from the client app. It depends on how you want to implement this. Ofcourse you need to have ADO reff in your dlls.

[tsd_man]

My idea:
1)client app will utilise a flexgrid retrieving data from a recordset obj (reference to ADO recordset object etc needed?)

2) the first DLL will handle the open and close connections stuff
(another reference the ADO DB object here?)

3) the second DLL will handle only the commands/instructions and passing any data (all SQL stuff from the Database). Also must receive info from the client app and pass it on to the DB
(another reference the ADO DB object here?)

hopefully this should make the idea clearer.

I thought that I would to have references to the ADO(ADODB) in the DLLs( module classes) and an reference to the class in the client app ...yes?

[tr0n]

i think it would be better to have one DLL that handles both the opening/closing of connections, as well as retrieving/sending data.

firstly, it would seem a bit pointless to have a DLL that only opens and closes connections (that's just gonna be like four small methods, two for the connection object, and two for the recordset). secondly, if you had the connection in a seperate DLL, you'd have to pass the connection between DLLs, which would seem to me to be unneccessarily complicated.

and yeah, i think you'd have to have ADO referenced in the client app, to pass the recordset to the flexgrid though.

hope that helps.