SQL packages

G'day all

We have an 'in house' VB application that uses SQL to update an AS400
database. An insert statement is generated which has a sub-select. This
statement is always written to the SQL package which then takes less than
two weeks to fill up (we have the 500mb / 16000 limit). The "where" part of
the subselect is always different as contains a list of "part ids" which are
system generated.

The IBM site states that an Insert with a sub-select will always write to
the package, however another section does point to a problem with packages
filling up because literals & parameter markers in the same statement are
not catered for correctly. Our statement uses parameter markers but has no
literals.

Does anyone know if we have genuine error or just a situation to be resolved
by other methods such as writing a stored procedure for the insert.

Regards

Tony Legros

My apologies if this is not the correct forum - I couldn't see an SQL
specific one.