[AccessD] Reporting field properties

That's what I thought.  In cases like this it is useful to be able to get at
the physical layer.  DAO is occasionally still useful.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Friday, July 15, 2005 2:36 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Reporting field properties


On 14 Jul 2005 at 23:25, John W. Colby wrote:

> I have tried the same thing with the ADODB.Field object but there is 
> nothing like the wealth of properties that DAO makes available, and I 
> see nothing like SourceTable and SourceField.
> 
> Anyone know if this is possible with ADO?
> 

ADO is an "abstraction layer" between the data source and your application.
The whole idea is that you don't need to know anything about the physical 
storage methods behind the recordset that you are working with.  AFAIK, 
there is no way with an ADO recordset to tell where a particular piece of 
data came from.

-- 
Stuart


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com