One recordset for every table. Is it good practice???

From: "Sergi" <sezmillenium@xxxxxxxx>
Date: Wed, 25 May 2005 11:19:12 +0200

HI people,

I have a VB application with DAO and i am migrating it to ADO. In this
application, first of all, I connect to database and I open a ado recordset
for each table in database.
If i need some information of table, i use this recordset. It is a good
practice???

Is better open a recordset with table only when I need it???

.

Follow-Ups:
- RE: One recordset for every table. Is it good practice???
  - From: Cam
- Re: One recordset for every table. Is it good practice???
  - From: Stephen Howe

Prev by Date: Best practices in ADO
Next by Date: Re: One recordset for every table. Is it good practice???
Previous by thread: Best practices in ADO
Next by thread: Re: One recordset for every table. Is it good practice???
Index(es):
- Date
- Thread

Relevant Pages

Re: Is ADO Dead (3)?
... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
(comp.databases.ms-access)
Re: Is ADO Dead (3)?
... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
(comp.databases.ms-access)
Re: Is ADO Dead (3)?
... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
(comp.databases.ms-access)
Re: Is ADO Dead (3)?
... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
(comp.databases.ms-access)
Re: Knowledge Base Help Not working
... Database is a DAO object. ... both Access 2000 and 2002 use ADO. ... Microsoft DAO 3.6 Object Library, ... For example, to ensure that you get a DAO recordset, you'll need to ...
(microsoft.public.access.formscoding)