A closer look at the SQL generated by the loader gave me this:
Code: Select all
EXECUTE BLOCK
(P0_0 INTEGER =?,P0_1 INTEGER =?,P0_2 INTEGER =?,P0_3 INTEGER =?,P0_4 DOUBLE PRECISION =?,P0_5 VARCHAR(0) =?,P0_6 INTEGER =?,
P1_0 INTEGER =?,P1_1 INTEGER =?,P1_2 INTEGER =?,P1_3 INTEGER =?,P1_4 DOUBLE PRECISION =?,P1_5 VARCHAR(0) =?,P1_6 INTEGER =?)
AS BEGIN
INSERT INTO ODVPOSET("MODEL","POSITION","SEQUENCE","TYPE","NUMVALUE","STRVALUE","UNIT")
VALUES (:P0_0,:P0_1,:P0_2,:P0_3,:P0_4,:P0_5,:P0_6);
INSERT INTO ODVPOSET("MODEL","POSITION","SEQUENCE","TYPE","NUMVALUE","STRVALUE","UNIT")
VALUES (:P1_0,:P1_1,:P1_2,:P1_3,:P1_4,:P1_5,:P1_6);
ENDI have tried to specify a string size explicitly on field definition, but this has not helped.
I have put together a small demoproject that should reproduce the problem with all relevant source. Please send me an email for a link to the project
I hope you can help me resolve this issue