ACTEBS
actebs at actebs.com.au
Tue Sep 28 08:32:42 CDT 2004
Jim, I would love to get a copy... Regards Vlad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim DeMarco Sent: Tuesday, 28 September 2004 2:28 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Elegant Solution? I have one for VB but it can easily be modded if you're using <A2K. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mark Breen Sent: Monday, September 27, 2004 11:58 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Elegant Solution? Hello All, Does anyone have a similar class or function for elegantly handling ADO record sets ? Or similar in the .Net environment ? Mark Breen Ireland On Mon, 27 Sep 2004 08:45:22 -0700, Charlotte Foust <cfoust at infostatsystems.com> wrote: > The difference is that if you use CurrentDb, you don't have to refresh > to see the changes. DBEngine is faster because it doesn't refresh > automatically. Redo your test with a refresh after every change and > see how they compare. > > Charlotte Foust > > > > > -----Original Message----- > From: Dan Waters [mailto:dwaters at usinternet.com] > Sent: Friday, September 24, 2004 7:06 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [AccessD] Elegant Solution? > > Using CurrentDB everywhere is slower. > > I use: > Set rst = DBEngine(0)(0).OpenRecordset(stg,db.....) > > I did a test once and determined that using the above line is exactly > 8 times faster than using: Set rst = > CurrentDB.OpenRecordset(stg,db.....) > > However, you must use CurrentDB for some things, like setting the > current database's properties in VBA. > > Dan Waters > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bobby Heid > Sent: Friday, September 24, 2004 6:19 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [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 > > -- > _______________________________________________ > 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 > > > -- > _______________________________________________ > 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 ************************************************************************ *********** "This electronic message is intended to be for the use only of the named recipient, and may contain information from Hudson Health Plan (HHP) that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately, either by contacting the sender at the electronic mail address noted above or calling HHP at (914) 631-1611. If you are not the intended recipient, please do not forward this email to anyone, and delete and destroy all copies of this message. Thank You". ************************************************************************ *********** -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com