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

Hello Jim,

Thanks for that, actually it may not be such a big issue if as they
say, ADO / MDAC is already installed.  It did not fear adding the
reference, thats the easy bit is was the expectation of hundreds of
references, but probably we will not see hundreds.

Thanks again.

Mark





On Mon, 17 Jan 2005 18:30:58 -0800, Jim Lawrence <accessd at shaw.ca> wrote:
> Hi Mark:
> 
> ADO is dependant on the MDAC files stored in the 'Program Files\Common
> Files\System\ado' directory. Every Windows OS from 98 has it setup that way.
> The alternative is to add an appropriate ODBC connection to every PC.... I
> have been that route and believe me using ADO is a piece of cake in
> comparison. At one point I had over 65 computers connected using a variety
> of OS versions, all over the country, many with different connection
> standards and most of offices I have never been to.
> 
> The only time you could run into issues is if you are getting too fancy with
> your ADO calls... not all versions of ADO support streaming or data shaping.
> If you did you could simply broadcast out the latest version and have it
> placed in the above mentioned directory.
> 
> HTH
> Jim
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Breen
> 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 new
> mdbs
> 
> 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
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>