OLEDB / ODBC Problems

Posted in 2000

Topics: Error Codes & Troubleshooting, Connectivity: ODBC / JDBC / .NET

Martin Keller — Tue, 22 Feb 2000 09:24:28 +0100 — source: Informix-list mailing list archive (1991-1998)

Hi, does anyone have solutions / workarounds for the following problems with IIF 2000 on Win NT ? 1. When updating text columns with the OLEDB-Provider, the provider crashes, if the text is exactly 64 bytes long. 2. We tried to use more than one database-connection in one process with the ODBC-Driver via ADO/OLEDB. In some cases, ADO returns an error code 0x8000FFFF when openig a recordset on the second / third connection. with regards M. Keller mailto:martink@u-planet.de

↪ replying to Martin Keller

Leopold The Cat — Tue, 22 Feb 2000 02:08:43 -0800 — source: Informix-list mailing list archive (1991-1998)

Martin, Is this Informix OLEDB provider (from ClientSDK)? If it is, can you post the repro (<100 lines of VB or C++ code, ADO or OLEDB)? Please also post the versions of ClientSDK and server. Thanks, Leopold Martin Keller <MartinK@u-planet.de> wrote in message news:88tidj$433$1@news.xmission.com... > > Hi, > > does anyone have solutions / workarounds for the following problems with IIF > 2000 on Win NT ? > > 1. When updating text columns with the OLEDB-Provider, the provider crashes, > if the text is exactly 64 bytes long. > > 2. We tried to use more than one database-connection in one process with the > ODBC-Driver via ADO/OLEDB. In some cases, ADO returns an error code > 0x8000FFFF when openig a recordset on the second / third connection. > > with regards > > M. Keller > > mailto:martink@u-planet.de > >