[AccessD] BE Relinker

Yes of course you are correct.  OTOH I have "retrofitted" an entire
application searching for objects and replacing them with DAO.ObjectName.
It helps that I have a standard naming convention of course.  But it took an
hour or two to do dozens of modules.  Then it is done and you don't have to
depend on reference order. 

My point is that depending on the compiler to "figure it out" is a recipe
for hours spent down the line scratching your head when something goes
wrong.  

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 Reuben Cummings
Sent: Wednesday, June 20, 2007 9:37 AM
To: Access Developers discussion and problem solving
Subject: Re: [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