I guess my question can go in two directions. I create applications
that run multiple queries against a database. Generally speaking in the
past I have used a Data Control (calling it dat1) making it invisible
and have used this whenever i needed it.

dat1.databasename = app.path & "mydatabase.mdb"
dat1.recordsource = "my query"
dat1.refresh

Lately I have seen that most programmers instantiate this when they
need it. For example, in typical DAO style.

dim db as database
set db = OpenDatabase(app.path & "\mydatabase.mdb")

dim rs as recordset
set rs = OpenRecordsets("my table or query")

My question is this. Is it better to instantiate it whenever I use it
or just use one control throughout my program and re-open it when I
need it. Which is better on memory?

My question is not just for DAO, ADO also has a data control or I can
instantiate that as well.

Which is better on memory?

Your post doesn't seem to have to do with ADO.NET as you are asking about
DAO and ADO and using VB 6.0 syntax.



<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I guess my question can go in two directions. I create applications
> that run multiple queries against a database. Generally speaking in the
> past I have used a Data Control (calling it dat1) making it invisible
> and have used this whenever i needed it.
>
> dat1.databasename = app.path & "mydatabase.mdb"
> dat1.recordsource = "my query"
> dat1.refresh
>
> Lately I have seen that most programmers instantiate this when they
> need it. For example, in typical DAO style.
>
> dim db as database
> set db = OpenDatabase(app.path & "\mydatabase.mdb")
>
> dim rs as recordset
> set rs = OpenRecordsets("my table or query")
>
> My question is this. Is it better to instantiate it whenever I use it
> or just use one control throughout my program and re-open it when I
> need it. Which is better on memory?
>
> My question is not just for DAO, ADO also has a data control or I can
> instantiate that as well.
>
> Which is better on memory?
>

Yes, I apologize, I asked this question in the wrong group. Yes I am
referring to VB6.

*** Sent via Developersdex http://www.developersdex.com ***