[AccessD] 203 vs. 2007

Charlotte Foust cfoust at infostatsystems.com
Thu Jul 23 16:52:36 CDT 2009


Yeah, when ADO came on the scene back in 2000, I learned disambiguation
fast!  Makes it a lot easier to debug too and intellisense gives you the
right list of methods/properties/whatever.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, July 23, 2009 12:05 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] 203 vs. 2007

A better solution than changing the order of the references, for sure,
even though that worked.

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Thursday, July 23, 2009 8:14 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] 203 vs. 2007

Rocky,

Property exists in both DAO and ADO.  You need to disambiguate all
references to objects that exist in both models, i.e., DAO.Property.

Charlotte Foust 





More information about the AccessD mailing list