Hi Everyone,

I am wondering if anyone has ever manager to make use of an OLEDB provider (in this case MySql or SQL Server, or even SQLite) without actually installing the driver to the machine. It is not an urgent matter, just one of curiosity given one of the scenarios that I am currently dealing with. An idle thought if you will.

Cheers

The Frog

The Frog wrote:
machine running the code that attempts to utilize it, an error will be
raised.

Can't think of any reason why it should be possible! Would seem to be
similar to trying to automate Excel from Access without Excel being
installed!


"The Frog" wrote in message
news:a08c9dfc-cd2d-4e91-8346-19724a31b32e (AT) googlegroups (DOT) com...

Hi Everyone,

I am wondering if anyone has ever manager to make use of an OLEDB provider
(in this case MySql or SQL Server, or even SQLite) without actually
installing the driver to the machine. It is not an urgent matter, just one
of curiosity given one of the scenarios that I am currently dealing with. An
idle thought if you will.

Cheers

The Frog

Hi guys,
I kind of figured it would be that way but had to consider the
possibility of a wrapper around a .dll or something similar. I am
looking at pushing and pulling some data from SQLite files to speed
up populating my tables. ETL is a bit heavy handed for this, but
without being able to install the drivers I will have to do it that
way. Maybe its possible to put a wrapper around SQLite directly? I
have never tried it.

The Frog

--
Cheers

The Frog

On Wed, 1 Aug 2012 01:55:30 -0700 (PDT), The Frog
<mr.frog.to.you (AT) googlemail (DOT) com> wrote:

I'm very hazy on what OLEDB is compared to DAO, ADO, etc. However
DAO and ADO are part of the operating system and have been since
Windows 2000. So will those suffice for, at least, basic SQL Server?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Tony Toews wrote:
OLEDB is what is used by ADO to communicate with databases via OLEDB
providers. Most rdbms have native providers to allow direct access to them.
Some don't so the use of the OLEDB provider for ODBC is required to
communicate through a second ODBC layer.

DAO ccommunicates with Jet directly, and to other databases via ODBC.

them were installed, such as Access. Does one still have to go to MS and get
the Jet Components installer to get the Jet OLEDB provider onto a machine?
When installing SQL Server, there is an option to install the client
connectivity tools which include the native OLEDB provider as well as the
native ODBC provider, so I'm a bit doubtful that they are included with the
OS.