At 11:32 AM 13-03-02 +0100, Lucas Franzen wrote:

>it only works okay if the statement looks like:
>INSERT INTO MYTABLE
>( MY_ID
>, MY_INTEGER)
>VALUES
>( 1
>, 2 )
>
>If the table name is added it doesn't work either.

Luc,
Confirmed, some DSQL change between RC2 and FB 1 broke the insert parsing
for datasets (both IB_Cursor and IB_Query). Update and Delete seem
unaffected - it is just the part of the parsing that creates an insert
statement containing the table identifier in the columnlist. ib_dsql is OK.

A check with my SQL standards book seems to indicate the change in the DSQL
(to forbid table identifiers in the insert column list) is correct. Still,
it's not very "correct" to make an unannounced implementation
changes...darn, I'm annoyed with myself, because I've tested every IBO
sub-release with every FB landmark - except THIS one. Too busy writing the
release notes. :(

The error you will get on dataset inserts is ERRCODE = 335544569 (-104
Unknown token . <-- this is the period following the first table identifier)


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com