Raik Thalheim wrote : >Hello Thomas,
>thanks for your reply. >Actually i get an (100) error code after >execute the SQL-String. > >AT>if $rc <> 0 then stop (-31001, "unexpected error " || chr($rc)); >---> unexpected error 100 > >I can execute the statement without any errors when i >execute the statement directly in the dbproc. > >CREATE DBPROC CREATE_KST_LEISTUNG(IN int_Test Integer) AS >VAR > > INSERT INTO .... > SELECT ... FROM > > >However, thank you. > >-- >Best regards, >Raik Thalhheim > >>i want to execute an SQL-statement generated by >>an sub-dbproc (see the example code please). >>I can call the CREATE_KST_LEISTUNG dbproc >>but the SQL-statement does not executed by the caller dbproc. >> >>Where is my mistake? >> AT> Actually I can't see anything wrong. But how did you verify that the statement AT> has not been executed ? Maybe the statement execution just returned an error. AT> I recommend to check the sqlcode after the statement execution : AT> CREATE DBPROC CREATE_KST_LEISTUNG(IN int_Test Integer) AS AT> VAR AT> SQL_KST_PRO_LST VARCHAR(8000); AT> call GET_STRING(:SQL_KST_PRO_LST); AT> execute SQL_KST_PRO_LST; AT> if $rc <> 0 then stop (-31001, "unexpected error " || chr($rc)); You are really sure that you executed exactly the same statement in both cases ? I assume that at least in the second case you have been forced the to specify complete table names (<owner>.<table name>). Did you do that in the first case too ? If not, you may have selected different tables. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
