Subject Re: [IBO] FieldValues[..] etc
Author staff@belding
Thanks Geoff for your reply. We are into the "trimming debate" again. It
would seem IBO has trimmed my string, but I say this without knowing the its
code, and latching onto this conclusion from the past discussion about
trimming and your remarks.

The phrase "controls designed for normal printable text" is, I'll bet,
nowhere to be found in IBO's self description. (I'll buy you lunch one day
if I'm wrong). My thinking is IBO should never trim users data and I recall
you appreciate IBO's trimming because you deal a lot in "printable text
data". My experiments suggest neither IBConsole not IBWorkbench use trimming
on strings.

By setting the Query properties for the Column in question to Trimming=NONE
my problem is solved.

Thanks again Geoff. I am still getting used to these idiosyncrasies in IBO.


----- Original Message -----
From: Geoff Worboys <geoff@...>
To: <>
Sent: Tuesday, June 19, 2001 1:28 PM
Subject: Re: [IBO] FieldValues[..] etc

> > A string in the database consists of three characters whose
> > hex values are 78,F0, 0C, inserted by encrypting another
> > three character string.
> >
> > When this string is IBO-retrieved it becomes a two character
> > string 78,F0 as seen in the TIB_GRID and as retrieved by
> > FieldValues.
> >
> > By contrast the string shows as three characters in the
> > Borland IBConsole display of the IB Table data, and in the
> > SQL_Grid for displaying data in IBWorkbench beta version
> > 0.8.5 (it uses IBObjects but I don't know which version).
> > I do not have IBO source.
> >
> > Anyone have any insight to this error?
> So what is displayed in IBConsole or IBWorkbench for the formfeed
> character?
> The difference may well be simply the choice of font, or possibly IBOs
> trimming is removing the character (you may need to use the new
> RawString properties).
> This sort of data will always cause difficulties within controls
> designed for normal printable text. I strongly suggest that you
> implement the encryption so that it generates either hex or b64 data
> so that it can be viewed and manipulated reliably.
> Geoff Worboys
> Telesis Computing
> Your use of Yahoo! Groups is subject to