Sergio Samayoa > > Check if the values have trailing spaces (already with 63 > chars ocuped) and > adding the new one makes it more than 63 chars long. Also if > your source > field is CHAR, according to data type semantics, the field already has > trailing spaces. > > "Juchem, Matthias" <[EMAIL PROTECTED]> escribi� en el mensaje > B2F8810683F0EA49877F866B241A2F300256344A@dewdfx16">news:B2F8810683F0EA49877F866B241A2F300256344A@dewdfx16... > > Hi. > > > > I have a DBPROC that interates over one tables and inserts values in > another. > > > > Somewhere it says 'Char value too long'. The DBPROC inserts > exactly one > character value per step, but the longest one is 23 > characters long, while > the column is of type VARCHAR(63); so is the variable in the > DBPROC that > deals with the value. > > > > I other words, this character value cannot be the source of > the error and > I have no idea where this error can come from. > > > > Is there a way to make SAPDB more verbose regarding error > messages? In > such cases, it would always be great to know which value is too long > respectively which column is too small. > >
The function LENGTH will NOT count trailing blanks. We know of a problem where trailing blanks are not truncated as they are usually during handling. I have no good imagination how your dbproc may look like, but please try to use TRIM or RTRIM to cut your value to the correct length (excluding) trailing blanks. In the situation we saw this problem before, this helped. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
