Hi Sam, Thanks, I somehow thought the default maxlen was 255 chars, so I thought there was sth with unicode translation... That did the first part, I changed the maxlen to 100 which was 50 before.
Thanks again... Teoman "Sam Jones" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > The default MAXLEN for %STRING is 64, this is why your data > got truncated (it probably contained some Unicode characters). > You can change this in the inspector for your string properties.. > > I'm not sure what you can do about the sort ordering problem. > > "Teoman Haliloglu" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Hi all, > > > > Cache does not support Turkish by default, so I did the Cache installation > > as Unicode when I first installed Cache. (Setup warned me about unicode > > setup is irreversible) > > > > So far I haven't faced any problems with this configuration. > > > > But today I've tried migrating data into Cache from an SQL Server database > > with an nvarchar field of length of 100. The counterpart field in Cache is > > of type %string. > > > > Then I linked to the original table from Cache, wrote a method which while > > browsing all the records in the original table, creates and saves new > > objects in the Cache application. The method worked fine, except for the > > fact that only the first 51 characters in the original field was > translated > > into Cache. > > > > Also when I sort records according to the name, any Turkish characters > > appear in the end of the list. > > > > So, 2 problems: > > > > 1. How can I correctly (full length) get the text fields? > > 2. How can I write/apply a sort order for a language not supported by > Cache? > > > > Any ideas? > > > > Thanks, > > Teoman > > > > > > > > > >
