We have a client trying to use our ODBC "Spy" Driver with MS
Access 2.0.  Their development environment is MS Visual Basic
3.0.

Our "Spy" driver must use another ODBC driver to do the actual
interaction with the underlying database (just for a quick
explanation without disclosing any trade secrets! :-)

The Problem:
------------
In order to use ODBC, our client switched from using the Jet
Engine to using ODBC API calls within his VB project.  Things
ran smoothly until he tried to access his data from a data
control.  His error message said basically, "If you want to use
this data control with MS Access, you gotta use the Jet Engine."  
Apparently, it would work fine with a different database and
ODBC.

The Restrictions:
-----------------
Our client cannot invest any more time trying this with other
databases.  Our client does not have VB 4.0.  Our client does
not have MS Access 7.0.

We have VB 4.0 and MS Access 7.0, but do not have our client's
versions.

The Questions:
--------------
1) Does anybody know if this is really possible with Access 2.0
and VB 3.0?

2) Does anyone out there know of a data control that is "ODBC
Friendly" to MS Access?

3) On a different note:  Does anyone know of an ODBC driver for
MS Access that supports the SQLPrimaryKeys function?  The one I
have (from Microsoft) does not.

If I have been at all unclear in this post, please e-mail me and
I'll try to explain further.

Thank you for your time!

Please Note:  I've set Followups to the
comp.lang.basic.visual.database newsgroup.
--

Hi,

I have been trying to use ODBC with Access within a VB
application, and have been unsuccesful, as VB returns with the
error saying that you cannot use ODBC on an ISAM database or
something like that.  It appears that you cannot use an Access
ODBC driver in VB applications.

Hope this helps,

JP

Why are they doing this at all? You are going nowhere with this so give them back their
money. If they are trying to figure out why a network app bogs the network or why a
query does not work right, etc, they need to employ a consultant that already knows
what, how, and why to do what is required of these type applications.

[snip]

To avoid the "you must use Jet to open an Access database" error,
have the user temporarily de-install the Access 2.0 Compatibility
Layer. This will cause the VB app to use the Jet 1.1 engine,
which will open Access 2.0 ODBC data sources. The old VBDB300.DLL
file in particular file will have to be reinstalled from the
original VB 3 diskettes or CD.

--

WARNING: I cannot be held responsible for the above        They're   coming  to
because  my cats have  apparently  learned to type.        take me away, ha ha!