Subject | Re: [IBO] TIB_ColumnText and strings that are too long |
---|---|
Author | Lucas Franzen |
Post date | 2006-01-10T17:58:22Z |
Martijn,
Then they see: CUSTNO - VARCHAR (40)
When they double click it they can change the properties of the field.
If they change it to 65 - their fault :-)
It is shown clearly that 40 is the maximum, the database (table) cannot
save more chars.
Some customers don't work with field length, they define it variable and
use field delimiters instead.
So if they give me a 10 char long customer no that's padded with tons of
blanks it will still work and they don't even see it was cutted.
And if they have the field delimiter as part of the data - their fault,
too :-)
Luc.
> I'll have to add my main complaint:For example they add the field CustomerNo to the interface.
>
> How do your users KNOW they defined something in the wrong way.
Then they see: CUSTNO - VARCHAR (40)
When they double click it they can change the properties of the field.
If they change it to 65 - their fault :-)
It is shown clearly that 40 is the maximum, the database (table) cannot
save more chars.
Some customers don't work with field length, they define it variable and
use field delimiters instead.
So if they give me a 10 char long customer no that's padded with tons of
blanks it will still work and they don't even see it was cutted.
And if they have the field delimiter as part of the data - their fault,
too :-)
Luc.