Have you guys tried the Intersolv driver?  I haven't come across the same
situation you have, but that driver has worked really well for me.
--
Regards,
Jim

 I am in need of assistance in locating a 'good'  ODBC driver for use with
MS Access, VB and Oracle.

I was using Access 95 with an Oracle ODBC driver (sqo32_73.dll  v.
2.00.0301) when I discovered that Access was defining an Oracle field with
scale 0 and precision 5, as type INTEGER.  Needless to say, there are values
higher than 32767 in that field.  Looking through the KB, Microsoft states
that it will map a field with scale 0 and precision 5 as a LONG_INTEGER.

Further research, suggested that I attempt to use a different application to
test.  Using MS Query (with the Oracle driver, I believe), MS Query had no
problem returning records where the value in the specific field was > 32767.

At this time, I noticed that I had a Microsoft ODBC driver for Oracle
(msorcl10.dll v 2.00.006325) on my system.  It comes with VB5.  So I
switched to that driver and attempted to query within Access that field that
was causing problems.  It worked no problem.

Thinking my problem would be solved, I then attempted to query a different
table.  I can't even open this table.  I receive an error:

    [Microsoft][ODBC driver for Oracle][Oracle]ORA-01858. a non numeric
character was found where a numeric was expected. (#1858)

The strange this is this:  We have 2 Oracle tables whose structure is
exactly the same.  One of the tables holds just last month's data.  The
other table holds the same data plus previous months'  data.  I can open up
the later table but not the former one.   Arrrgghh.

So as of now, neither of these two drivers are satisfactory.  Can anyone
either, provide a solution or make a recommendation on a reliable ODBC
driver for Oracle, and if so, where can I obtain said driver?

I apologize for the length, just wanted to stress that I have been through
the KB and have done hours of testing to narrow down what is actually
happening.  TIA.

-------------------
David R.

Replies in the newsgroups help out others who might have the same problem.

We got *exactly* the same problems with Access 97, an Oracle table
linked and a field numeric(5) converted into integer, with values >
32k.
Actually we have no solution, keeping hope in newsgroup help messages.
I will write down here our assistance as soon as we find  the good
ODBC  driver.

Bernard
------------------

wrote :

David,

You might try my company's ODBC drivers for Oracle.

A free trial of SimbaExpress and Oracle ODBC drivers are available from our
web site: http://www.simba.com.

Randy
Simba Technologies

 I am in need of assistance in locating a 'good'  ODBC driver for use with
MS Access, VB and Oracle.

I was using Access 95 with an Oracle ODBC driver (sqo32_73.dll  v.
2.00.0301) when I discovered that Access was defining an Oracle field with
scale 0 and precision 5, as type INTEGER.  Needless to say, there are
values
higher than 32767 in that field.  Looking through the KB, Microsoft states
that it will map a field with scale 0 and precision 5 as a LONG_INTEGER.

Further research, suggested that I attempt to use a different application
to
test.  Using MS Query (with the Oracle driver, I believe), MS Query had no
problem returning records where the value in the specific field was >
32767.

At this time, I noticed that I had a Microsoft ODBC driver for Oracle
(msorcl10.dll v 2.00.006325) on my system.  It comes with VB5.  So I
switched to that driver and attempted to query within Access that field
that
was causing problems.  It worked no problem.

Thinking my problem would be solved, I then attempted to query a different
table.  I can't even open this table.  I receive an error:

    [Microsoft][ODBC driver for Oracle][Oracle]ORA-01858. a non numeric
character was found where a numeric was expected. (#1858)

The strange this is this:  We have 2 Oracle tables whose structure is
exactly the same.  One of the tables holds just last month's data.  The
other table holds the same data plus previous months'  data.  I can open up
the later table but not the former one.   Arrrgghh.

So as of now, neither of these two drivers are satisfactory.  Can anyone
either, provide a solution or make a recommendation on a reliable ODBC
driver for Oracle, and if so, where can I obtain said driver?

I apologize for the length, just wanted to stress that I have been through
the KB and have done hours of testing to narrow down what is actually
happening.  TIA.

-------------------
David R.

Replies in the newsgroups help out others who might have the same problem.