Good morning, Peter,



I have had experience with strings being too long and the save operation failed because of it. The data server will not truncate automatically and I know SF does not do this.



If you do change the length of the column, then a visit to the BOM is in order. Definitely recompile.



It is quite odd that an nvarchar data type with a max length of 20 would allow a set of characters with a length of 22.



Hope you get this one figured out!

Bill

Hi,



We had a curious issue today. A form exceptioned because column length value (by mistake) in the database was too short - just 20 characters when it should have been 100.



The database was corrected but in testing I noted that when I entered 40 characters what is saved to the database is 22 characters. If enter 40 characters in EM then no problems so it is something in the form. So, I assume the truncation must be happening in the BO and what I didn't do is remap and compile the BO after I changed the column length.



So, a few questions:



1) Does SF trim form data to the maximum a column can accept during the Save operation.



2) If 1 is true then after changing column lengths does the associated BO need to be recompiled.



3) If 2) is true then it would appear there may be a bug in the SF code in that a nvarChar(20) column is being saved with 22 characters not the 20 as was originally mapped.



BTW we use DevExpress but I can't see how that would effect things.



Cheers, Peter