preethi
15th September 2010, 12:42
Hi,

i have created a table & a maintain session. The maintain session takes PO number Receipts Number as input and captures the login ID & date. this data is to be saved in the table created.

When Save button is pressed it is giving error: cannot continue

i have checked in log.informix for the log message it is
" number of columns in INSERT doesnot match number of VALUES"
can any body explain what might be the cause for the error.

Thanking you in Advance

croezen
15th September 2010, 12:44
plz post your code so we can talk a look

bdittmar
15th September 2010, 13:07
Hi,

i have created a table & a maintain session. The maintain session takes PO number Receipts Number as input and captures the login ID & date. this data is to be saved in the table created.

When Save button is pressed it is giving error: cannot continue

i have checked in log.informix for the log message it is
" number of columns in INSERT doesnot match number of VALUES"
can any body explain what might be the cause for the error.

Thanking you in Advance

Hello,

set your session in debugger mode and analyse the error message if number of values are identical with number of columns at insert statement.

Regards

preethi
15th September 2010, 15:10
i actually didn't user any insert command....

i am a novice in this field..so bdittmar can u explain in detail?i hav also run the session in debug mode..the program is halted in before.write

BaanInOhio
15th September 2010, 16:26
Run general table maintenance (ttaad4100) for the table and attempt to add a new record. If it works, the problem is in your program script. An error in GTM indicates a database issue. If database, I would investigate the table to see if your convert to runtime (or create) was successful.

Your issue sounds like a mismatch between the Baan database definitions and informix = typically an index or field that differs between the two. If I am unsure, I may completely delete the table and create it again under a slightly different name. I have seen this error in the past when a table is created, eventually deleted, then a new table is created with the same name (different fields/indexes). Informix may still have some information based on the old, not new definition of the table.