× 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.



I have a customer with an app that connects to the i with ODBC. It is an ancient application running on Windows NT but has worked flawlessly for a decade. They upgraded to V7R1 from V6R1 and now they get the following on any SQL invoked by the ODBC connection:

Message ID . . . . . . : SQL0084 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 10/01/12 Time sent . . . . . . : 16:31:12

Message . . . . : SQL statement not allowed.
Cause . . . . . : The SQL statement is not allowed for one of the following
reasons: <Lists a bunch of reasons here>

Of course, stating what the offending statement IS apparently isn't part of the error reporting so I don't know which of a few hundred SQL statements it is complaining about. I am assuming it is the initial CONNECT but I can't be sure.

Anyone run into this? I can find much in the Memo to Users that refers to ODBC or SQL0084

Thanks,


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.