× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: ODBC - rdoQuery
  • From: "Nelson, Jim (RCIS)" <Jim.Nelson@xxxxxxxxxxxx>
  • Date: Thu, 15 Apr 1999 17:44:15 -0500


We are stuck.

Have a VB application that connects to the AS/400 using ODBC.  In March, we
started getting a large number of communication link failures.

Happens in several different parts of the application, on SELECT, UPDATE and
DELETE commands, different tables, etc.  The only common denominator found
so far is that it happens when we are using rdoQuery.

This is the error that is captured:
Error #40002, Description: 08S01: [IBM][Client Access ODBC Driver
(32-bit)][DB2/400 SQL]
Communication link failure. Comm RC=0x17, Source: MicrosoftRDO.RdoQuery,
SQL: 

Has anybody had a similar experience?  In some situations, the user will
exit the application, which should drop the connection.  When they get back
into the app, it appears that the original connection is still used.  Seems
to work fine except for the rdoQuery.

Thoughts?

Thanks, JN



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.