[AccessD] DAO and ADO problem =>urgent! <SOLVED!>

wow, and then there was silence....

Very nice, thnx a lot.

SD
--- John Colby <jcolby at colbyconsulting.com> wrote:
> SD,  Add your own error handling.
> 
> Go to www.DatabaseAdvisors.com .
> Click Downloads.
> Click VBErrorHandler
> Expand in a directory of your choice and follow the
> instructions in the
> readme.
> Once installed, this allows you to create error
> handlers in a single
> function, or all functions in all of the modules in
> the reports, forms or
> module tab.
> 
> Very handy.
> 
> Of course, ALWAYS back up the FE before starting.
> Do one set (Modules), compile to ensure no errors.
> Do the next (forms), compile to ensure no errors.
> Do the last (reports), compile to ensure no errors.
> 
> You now have an error handler in every function in
> your entire FE.
> 
> A fine piece of Engineering work brought to you by
> myself and Seth Galitzer
> 
> John W. Colby
> www.colbyconsulting.com
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On
> Behalf Of Sad Der
> Sent: Thursday, August 14, 2003 1:17 AM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] DAO and ADO problem =>urgent!
> <SOLVED!>
> 
> 
> thnx for the follow up.
> 
> Bob, charlotte, you're (of course) both correct.
> However, I've only enherited this beast. If only you
> could see it....(to big, law issues :-). Rework
> alone
> could keep me of the streets for about a fortnight.
> 
> I mean, why would anybody add error handling? There
> isn't any, go figure!
> 
> ah well, almost weekend :-)
> 
> SD
> --- Charlotte Foust <cfoust at infostatsystems.com>
> wrote:
> > Actually, it's ADODB.Recordset for ADO.
> >
> > Charlotte Foust
> >
> > -----Original Message-----
> > From: Bob Hall [mailto:rjhjr at cox.net]
> > Sent: Wednesday, August 13, 2003 4:13 PM
> > To: Access Developers discussion and problem
> solving
> > Subject: Re: [AccessD] DAO and ADO problem
> =>urgent!
> > <SOLVED!>
> >
> >
> > On Wed, Aug 13, 2003 at 03:36:06AM -0700, Sad Der
> > wrote:
> > > AAHRG, did some testing and DAO 3.0 instead of
> 3.6
> > was referenced! Now
> >
> > > it works again.
> >
> > You should still follow Stuart's suggestion; e.g.
> > 	Dim rs As ADO.Recordset
> > Otherwise, VBA won't know whether you want an ADO
> or
> > DAO recordset,
> > and may choose the wrong one.
> >
> > Bob Hall
> > _______________________________________________
> > 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
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> http://sitebuilder.yahoo.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


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com