[AccessD] BE Relinker

I think most of us do.  I know I do as well.  My point was if you have a lot
of DAO code already in place you can use ADO code by making the ADO
reference after DAO and simply dimensioning the ADO stuff correctly.  The
DAO stuff will still work fine then.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of jwcolby
> Sent: Tuesday, June 19, 2007 10:14 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] BE Relinker
>
>
> I do too.  Part of the dimension statement is to allow the
> developer to read
> what things are.  DAO.Database plainly states that it is a part of the DAO
> model.
>
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
> Sent: Tuesday, June 19, 2007 9:57 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] BE Relinker
>
> Same for me.  I even do this...
> Dim dbs As DAO.Database
> which is a bit pointless really, since ADO doesn't have a Database object
> anyway, so not much need to disambiguate.  Ah well...
>
> Regards
> Steve
>
> jwcolby wrote:
> > For myself, I declare everything explicitly regardless of references.
> >
> --
> 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
>