Re: CREATE PROCEDURE -- MIDRANGE-L

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

Found this at Crystal's site, in <http://support.crystaldecisions.com/library/kbase/articles/c2008274.asp>

IBM has an undocumented registry setting that is required when using Crystal Reports to call DB2 Stored Procedures on an AS/400 using the IBM Client Access Express ODBC drivers.

This setting is specified in the registry at: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<-my dsn->, must be added as AllowProcCalls=1.

The same would apply to any user DSNs, so also look at HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\<-my dsn->, must be added as AllowProcCalls=1.

HTH

Vern

At 08:47 AM 2/19/2003 -0800, you wrote:

Has anyone created and procedure with SQL on the iSeries and successfully
used it in ODBC? Here's the message I'm receiving from Crystal Reports...

'ODBC Error: [IBM] Client Access Express ODBC Driver (32-bit) Statement
violates access rule: Connection is set to read only.'

I've tried many different combinations of settings within ODBC properties
and don't seem to get a combination that works.


Ken Slaugh (707) 795-1512 x118
Chouinard & Myhre, Inc.
CA/400 Certified Specialist
iSeries Network/MSE Administrator
http://www.cm-inc.com/

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.