Hi marco, sometimes it depends how your data is stored (check your local driver settings). Take ORACLE as an example where ordinary character colomns are padded with trailing spaces which have to be taken into account. So the 10 character string with the displayed value "myted" has to be seen as "myted " If the same is specified as VARCHAR with a length of 10, it is the expected "myted" end of show. "my*" anything fine if you enter the first characters and apply the *-wildcard at the end because this covers the characters as well as spaces. "*ted" hard if you want to see a text which ends with a given pattern because "myted" ends with ted, but "myted " doesn't, because of the trailing spaces.

ulrich-merkel said Hi marco, sometimes it depends how your data is stored (check your local driver settings). Take ORACLE as an example where ordinary character colomns are padded with trailing spaces which have to be taken into account. So the 10 character string with the displayed value "myted" has to be seen as "myted " If the same is specified as VARCHAR with a length of 10, it is the expected "myted" end of show. "my*" anything fine if you enter the first characters and apply the *-wildcard at the end because this covers the characters as well as spaces. "*ted" hard if you want to see a text which ends with a given pattern because "myted" ends with ted, but "myted " doesn't, because of the trailing spaces.

Hi Uli, thanks for your reply, I now that, but the same form on the same field in U8 works correctly, in U9 not. The field is char (oracle), maybe this is the problem? In char field always is padding with space to the size of field. Do you know if in U9 is changed something on char datatype? Marco

Hi Marco, I think the best is if you compare what your uniface documentation says for your special U8 and U9-version. And compare the driver settings in your ASN files as well as in the documentation. And you may ask your local CPWR contact for on-site assistance.