>>>
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));
AT> You are really sure that you executed exactly the same statement in both cases ?
AT> I assume that at least in the second case you have been forced the to
AT> specify complete table names (<owner>.<table name>).
AT> Did you do that in the first case too ? If not, you may have selected
AT> different tables.
AT> Best Regards,
AT> Thomas
Hello Thomas,
yes it is accurately the same.
I want to copy some values from one
temp-table into another. These tables
are created in the caller dbproc (CREATE_KST_LEISTUNG).
It is permitted by MAXDB to assign a string value
over several lines like this?
SET str_SQL = 'INSERT INTO "TEMP"."KOSTEN_PRO_LEISTUNG"
.....
SELECT min(LABOR),LABOR_ID,Min(KOSTENSTELLE)
FROM "TEMP"."BERICHT_GESAMTUEBERSICHT" GESAMT
WHERE
(GESAMT.LABOR <> ''Allgemein'') AND
...
...';
--
Best regards,
Raik Thalheim
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
