[AccessD] DAO vs ADO

People sometimes get confused finding their car in the parking lot.  ;-)

I made it clear in my posts that you MUST dim ADO/DAO things using the lib
prefix.  That is all I can do.

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 Charlotte Foust
Sent: Tuesday, May 15, 2007 2:09 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] DAO vs ADO

Yes, I know, but people sometimes get confused when the object have the same
names.

Charlotte 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, May 15, 2007 10:22 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] DAO vs ADO

>But I was specifically referring to trying to do things like creating 
>an
ADO recordset and using DAO parameters.

That you can't do, DAO and ADO are simply different beasts with different
methods and properties (and parameters).

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 Charlotte Foust
Sent: Tuesday, May 15, 2007 12:50 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] DAO vs ADO

You've had better luck than I then.  But I was specifically referring to
trying to do things like creating an ADO recordset and using DAO parameters.

Charlotte 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, May 15, 2007 8:31 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] DAO vs ADO

Charlotte,

>You can use both DAO and ADO in the same project but you can't mix them

>in
the same routine.

You absolutely CAN "mix them in the same routine".  The dimension statement
binds the variable to the correct object in the correct library and both can
be used "at the same time".

Function MixItUp()
	dim rstADO as ADODB.Recordset
	dim rstDAO as DAO.recordset

	.Initialize the ADO recordset here
	.
	.Initialize the DAO recordset here

	'Use both recordsets here for manipulating their specific data...

End function