How to resolve error SQL0113 
Author Message
 How to resolve error SQL0113
When I try to connect my crystal report through ODBC (AS/400 client access -
32 bits), it gives me error SQL0113 saying that "*N" member is not allowed !
How can I resolve this problem ?? Thx.........


Sat, 04 Jun 2005 23:52:48 GMT
 How to resolve error SQL0113

When I try to connect my crystal report through ODBC (AS/400 client
access -32 bits), it gives me error SQL0113 saying that "*N" member is not
allowed ! How can I resolve this problem ?? Thx.........


Sun, 05 Jun 2005 22:39:01 GMT
 How to resolve error SQL0113

I have the same problem too. But nobody can give me any sugesstion. Do
you know how to solve this problem now?

--
Posted via http://dbforums.com



Fri, 14 Oct 2005 22:19:47 GMT
 How to resolve error SQL0113

Hi,

i got the same error with Crystal reports and IBM Client Access ODBC
Driver.....i don't know exactly how to solve it, but i am pretty sure
that is an AS400 problem, because i have another as400 with a different
version of OS400 and there all works perfectly.... (???)

Here are the details :

Not Working OS400     V4 R4 M0

Working  OS400          V3 R2 M0

ODBC VERSION          Client Access Express 32 BIT V4 R5 M0

                                  Service Pack SF67276
good luck !!!

--
Posted via http://dbforums.com



Sun, 13 Nov 2005 17:55:44 GMT
 How to resolve error SQL0113

Quote:

> Hi,

> i got the same error with Crystal reports and IBM Client Access ODBC
> Driver.....i don't know exactly how to solve it, but i am pretty sure
> that is an AS400 problem, because i have another as400 with a different
> version of OS400 and there all works perfectly.... (???)

> Here are the details :

> Not Working OS400     V4 R4 M0

> Working  OS400          V3 R2 M0

> ODBC VERSION          Client Access Express 32 BIT V4 R5 M0

>                                   Service Pack SF67276
> good luck !!!

> --
> Posted via http://dbforums.com

Hello Pubetta,
     Is there any text accompanying the SQL0113 error code? If not, can you supply a client side ODBC trace that shows the problem in context? The following instructions will help you, should you decide to trace?
A. Open your ODBC Data Sources utility.
B. Enable tracing on the tracing tab.
C. Recreate the SQL0113 error condition.
D. Disable tracing on the tracing tab.
E. Locate the file indicated in the log file path on the tracing tab.
F. Post the file, probably as an attachment.
Netrista Khatam
Technical Services Manager
OpenLink Software
Universal Data Access Middleware
http://www.openlinksw.com


Sun, 13 Nov 2005 22:04:07 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. ADO error: Cannot resolve collation conflict for column n in SELECT statement

2. Trying to resolve those errors

3. Connection error resolved through help of Microsoft Support

4. Resolving Deadlock Error in VB Application

5. Getting 'Cannot resolve collation conflict..' error

6. Resolving BCP error reading Format file

7. replication error - how to resolve?

8. ODBC Error - how to resolve this?

9. How To Resolve SQL6.5 Fatal Error 702?

10. Need help to resolve the error message

11. cannot resolve error 1510 (sql 6.5)

12. SQL-Mail Adress-resolving error


 
Powered by phpBB® Forum Software