Subject Re: [IBO] TIBOTable Weirdness
Author Robert martin
Hi

Ok so if my VarChar is greater than 255 then .AsString will not
(neccasarily) return an empty string. Makes sense. It was just weird
in that it seemed to be working elsewhere. However I have found another
place where it fails today.

Thanks Jason & Hans

Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd



Jason Wharton wrote:
> Rob,
>
>
>> We have an application that is using TIBOTable (for legacy
>> reasons) that
>> has recently started to fail. We increased the size of a
>> field to 3072
>> characters (varChar) from about 70. Now when this field is accessed
>> using Table.AsString instead of returning an empty string
>> (when NULL) is
>> returns 8222 empty spaces. Table.IsNull returns true. It is
>> relatively
>> easy to fix the code (just use an isNUll test). However it
>> seems their
>> might be some bug with the code if the functionality changes with
>> increased field sizes.
>>
>> We are using IBO v 4.8.6
>>
>
> If the column is still type CHAR then this is expected behavior.
>
> Likely what is happening is the field type is now TMemoField instead of
> TStringField and the field trimming rules are not being applied.
>
> Jason
>
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>
>
>