[AccessD] Calling ADO without having to roll out five hundred newmdbs

With 97, there is no built-in ADO support as in 2002, which means you
need a reference.  You could put the reference into an MDA, along with
the code that uses it, but you are likely to run into problems if you
start mixing DAO and ADO calls within a routine.  You can't pass an ADO
recordset back to a routine that has no ADO reference to work with, if
that's what you had in mind.  If it isn't what you intended, explain
further.

Charlotte Foust


-----Original Message-----
From: Mark Breen [mailto:marklbreen at gmail.com] 
Sent: Monday, January 17, 2005 3:58 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Calling ADO without having to roll out five hundred
newmdbs


Hello All,

I just sent an email tell you about a new project that I have taken on.
It is Access 97 and Oracle as the BE.

We would like to use ADO for some stored procedures to avail of output
parameters, but it is not desirable to have to reference ADO on five
hundred PC's.  Especially with different versions of the OS throughout
the company.

Is there a way that I can call this ADO, from a central database and
pass the results back to the clients that are located throughout the
company?  Maybe MDA's?  I know that if I use MDA's that I will have to
reference them, but that might not be too bad because at least I can
control the version.  But that MDA will need the ADO reference.

I have not really done any COM / DCOM work, but maybe some of you have
and can think of a solution to this,

The alternative is to try to rev the access db with new references to
ado.

Thanks in advance for your help.

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