[AccessD] Elegant Solution?

I thought using currentdb everywhere used extra resources and was a no-no.

Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Erwin Craps - IT
Helps
Sent: Friday, September 24, 2004 3:57 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Elegant Solution?


I never do  dbs as DAO.Database


I always do 
Set rstTemp as currentdb.openrecordset (bla bla)

Dbs can be replaced by currentdb


Erwin


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of ACTEBS
Sent: Friday, September 24, 2004 9:13 AM
To: access group
Subject: [AccessD] Elegant Solution?

Hi Everyone,
 
Does anyone have any code or such that handles the following elegantly:
 
Dim dbs as DAO.Database
Dim rst as DAO.Recordset
 
Set dbs etc etc
 
Do whatever here
 
dbs.close
dbs = nothing etc etc
 
I am tired of having do the above to open database connections and
recordsets in the above manner in every Sub or Function. Surely there's a
more elegant method that someone has come up with here you just parse the
SQL Statement through or something...
 
Any suggestions or links will be greatly appreciated...
 
Regards
Vlad
 
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com