ODBC connection 
Author Message
 ODBC connection

I've installed an Informix OBDC driver on a Windows 2000 box last summer
to
establish PC access to Informix data on an HP-UX O/S.  Microsoft's IIS5
webserver uses this OBDC connection to serve up web pages with
live/dynamic
content from our Informix database.  It's been working just great!

I just installed Microsoft Access 2002 on this same PC today and have
been
having quite a bit of trouble trying to successfully "link" tables to
this
ODBC Connection.  ("Linking" tables in Access is effectively just
setting up
a view to an external table.  You can view/query the data as if it were
a
table local to Access, but really, the data is sourced from an external
database.)

The error I get is a complaint that "Microsoft Jet database engine could
not
find the object 'fen.opsi'.  Please check that the object exists and
that
you have typed its name and path name correctly."

The truth is that I didn't type anything at all.  The 'fen.opsi' is a
name I
selected from the list that Access presented (presumably what Access
detected from the ODBC driver).  The table is called 'opsissues' and is
owned by 'fenbers' in Informix, thus the name 'fen.opsi' indicates at
least
that Access partially knows what's going on.

I'm not sure if this is an Access problem, and Informix problem, or a
configuration problem on my part.  I doubt the latter because IIS5 is
able
to see the tables without a hitch, so it seems the ODBC connection is
indeed
set up right.

Any ideas??


  Sr. HAS Meteorologist
  DOC/NOAA/NWS/OHRFC



Wed, 02 Jun 2004 03:15:06 GMT
 ODBC connection

I have the same problem here.  The Informix ODBC Driver (version 3.80) works
fine on at NT machine, but on a 2000 machine, it truncates the Informix
table owner and Informix table name.

--
Jay Aymond
Community Coffee Company
Baton Rouge, LA
www.communitycoffee.com

Quote:

> I've installed an Informix OBDC driver on a Windows 2000 box last summer
> to
> establish PC access to Informix data on an HP-UX O/S.  Microsoft's IIS5
> webserver uses this OBDC connection to serve up web pages with
> live/dynamic
> content from our Informix database.  It's been working just great!

> I just installed Microsoft Access 2002 on this same PC today and have
> been
> having quite a bit of trouble trying to successfully "link" tables to
> this
> ODBC Connection.  ("Linking" tables in Access is effectively just
> setting up
> a view to an external table.  You can view/query the data as if it were
> a
> table local to Access, but really, the data is sourced from an external
> database.)

> The error I get is a complaint that "Microsoft Jet database engine could
> not
> find the object 'fen.opsi'.  Please check that the object exists and
> that
> you have typed its name and path name correctly."

> The truth is that I didn't type anything at all.  The 'fen.opsi' is a
> name I
> selected from the list that Access presented (presumably what Access
> detected from the ODBC driver).  The table is called 'opsissues' and is
> owned by 'fenbers' in Informix, thus the name 'fen.opsi' indicates at
> least
> that Access partially knows what's going on.

> I'm not sure if this is an Access problem, and Informix problem, or a
> configuration problem on my part.  I doubt the latter because IIS5 is
> able
> to see the tables without a hitch, so it seems the ODBC connection is
> indeed
> set up right.

> Any ideas??


>   Sr. HAS Meteorologist
>   DOC/NOAA/NWS/OHRFC



Wed, 02 Jun 2004 04:34:07 GMT
 ODBC connection

I bet it's a MDAC problem.  I think the Access 2002 installation process
updates MDAC (my personal nemesis) to 2.6, and the MDAC 2.6 update includes
Jet ver. 4.  Go to: www.microsoft.com/data, maybe you can find some useful
information there.

Quote:
-----Original Message-----

Sent: Friday, December 14, 2001 11:15 AM

Subject: ODBC connection

I've installed an Informix OBDC driver on a Windows 2000 box last summer
to
establish PC access to Informix data on an HP-UX O/S.  Microsoft's IIS5
webserver uses this OBDC connection to serve up web pages with
live/dynamic
content from our Informix database.  It's been working just great!

I just installed Microsoft Access 2002 on this same PC today and have
been
having quite a bit of trouble trying to successfully "link" tables to
this
ODBC Connection.  ("Linking" tables in Access is effectively just
setting up
a view to an external table.  You can view/query the data as if it were
a
table local to Access, but really, the data is sourced from an external
database.)

The error I get is a complaint that "Microsoft Jet database engine could
not
find the object 'fen.opsi'.  Please check that the object exists and
that
you have typed its name and path name correctly."

The truth is that I didn't type anything at all.  The 'fen.opsi' is a
name I
selected from the list that Access presented (presumably what Access
detected from the ODBC driver).  The table is called 'opsissues' and is
owned by 'fenbers' in Informix, thus the name 'fen.opsi' indicates at
least
that Access partially knows what's going on.

I'm not sure if this is an Access problem, and Informix problem, or a
configuration problem on my part.  I doubt the latter because IIS5 is
able
to see the tables without a hitch, so it seems the ODBC connection is
indeed
set up right.

Any ideas??


  Sr. HAS Meteorologist
  DOC/NOAA/NWS/OHRFC



Wed, 02 Jun 2004 04:49:23 GMT
 ODBC connection
I have two suggestions. First, don't use the ODBC driver by Informix. I have
found that Merant's driver is much better. This driver comes on the Informix
CD for free.

Second, try using some other tool like
WinSQL(http://www.indus-soft.com/winsql) and see if you have the same
problem. If you see the same problem in this utility, you will know if this
is an ODBC problem or MS Access problem.

Thanks,
Mike.

Quote:

> I've installed an Informix OBDC driver on a Windows 2000 box last summer
> to
> establish PC access to Informix data on an HP-UX O/S.  Microsoft's IIS5
> webserver uses this OBDC connection to serve up web pages with
> live/dynamic
> content from our Informix database.  It's been working just great!

> I just installed Microsoft Access 2002 on this same PC today and have
> been
> having quite a bit of trouble trying to successfully "link" tables to
> this
> ODBC Connection.  ("Linking" tables in Access is effectively just
> setting up
> a view to an external table.  You can view/query the data as if it were
> a
> table local to Access, but really, the data is sourced from an external
> database.)

> The error I get is a complaint that "Microsoft Jet database engine could
> not
> find the object 'fen.opsi'.  Please check that the object exists and
> that
> you have typed its name and path name correctly."

> The truth is that I didn't type anything at all.  The 'fen.opsi' is a
> name I
> selected from the list that Access presented (presumably what Access
> detected from the ODBC driver).  The table is called 'opsissues' and is
> owned by 'fenbers' in Informix, thus the name 'fen.opsi' indicates at
> least
> that Access partially knows what's going on.

> I'm not sure if this is an Access problem, and Informix problem, or a
> configuration problem on my part.  I doubt the latter because IIS5 is
> able
> to see the tables without a hitch, so it seems the ODBC connection is
> indeed
> set up right.

> Any ideas??


>   Sr. HAS Meteorologist
>   DOC/NOAA/NWS/OHRFC



Thu, 03 Jun 2004 01:59:53 GMT
 ODBC connection
Paul,

This is likely an issue that came up this summer.  Access is retrieving the
data (owner and table names)  through a function call that accepts data
buffer and max-length-of-data arguments.  The driver was considering the max
length as the number of bytes when Access was considering it to be the
number of characters.  I believe 'number of characters' is correct.  Also, I
think this is fixed at the latest release, SDK 2.70.TC3.  I'm guessing you
are using the Unicode-enabled 3.8 driver or maybe it's just that Access is
passing a Unicode (UCS-2) string.

IIS and Access are likely using differenct sets of ODBC function calls to do
the same kind of thing.

Luck,
Chris

Cc'ing you just in case you'd given up.


Quote:

> I've installed an Informix OBDC driver on a Windows 2000 box last summer
> to
> establish PC access to Informix data on an HP-UX O/S.  Microsoft's IIS5
> webserver uses this OBDC connection to serve up web pages with
> live/dynamic
> content from our Informix database.  It's been working just great!

> I just installed Microsoft Access 2002 on this same PC today and have
> been
> having quite a bit of trouble trying to successfully "link" tables to
> this
> ODBC Connection.  ("Linking" tables in Access is effectively just
> setting up
> a view to an external table.  You can view/query the data as if it were
> a
> table local to Access, but really, the data is sourced from an external
> database.)

> The error I get is a complaint that "Microsoft Jet database engine could
> not
> find the object 'fen.opsi'.  Please check that the object exists and
> that
> you have typed its name and path name correctly."

> The truth is that I didn't type anything at all.  The 'fen.opsi' is a
> name I
> selected from the list that Access presented (presumably what Access
> detected from the ODBC driver).  The table is called 'opsissues' and is
> owned by 'fenbers' in Informix, thus the name 'fen.opsi' indicates at
> least
> that Access partially knows what's going on.

> I'm not sure if this is an Access problem, and Informix problem, or a
> configuration problem on my part.  I doubt the latter because IIS5 is
> able
> to see the tables without a hitch, so it seems the ODBC connection is
> indeed
> set up right.

> Any ideas??


>   Sr. HAS Meteorologist
>   DOC/NOAA/NWS/OHRFC



Sat, 05 Jun 2004 12:40:02 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. odbc connection from a direct dial in connection

2. ODBC connection using Trusted Connection

3. ODBC connection using Trusted Connection

4. CRecordSet class and ODBC connections - Too many connections

5. Benchmark for ODBC connection and interactive connection

6. ODBC connection to DB2 on AS/400 and performance with protocols / port / connection

7. Repost - ODBC connection deadly slow odbc only on server, over LAN it's fine

8. ODBC-connection to BASIS ODBC Driver

9. ODBC Error 126 on Testing Filemaker ODBC Connection

10. Linked server ODBC connection

11. DTS - ODBC Connection timing out

12. ODBC connection and MSAccess


 
Powered by phpBB® Forum Software