At 06:40 AM 30/05/2003 +0000, you wrote:

>hello,
> I am a full time programmer, mainly on MCUs. from time to time I do
>small bussiness software, too.
>I was using...
>THSD qr design
>quick report
>custom GJLRXDBGrid, added check box support for interbase domain
>boolean field
>
>now I want to switch to IBO, but I'm concerning my needed features.
>the grid control I was using can save the column width in registry,
>so the user can customize it on their own, and more important, save
>my time from adjusting them.
>
>since I'm not making such software too often, I dont' want to invest
>too much.
>
>here are my questions.
>does IBO's db grid support run time column size saving? or can I use
>RX/project jedi's registry storage to store the column width easily?

If you are using the TIBODataset components, these use the VCL's
TDatasource and you can just stay with your RX grid. The TIB_ (native IBO)
grid's column attributes (incl. dimensions) are determined by attributes of
the data, so column width is set via the FieldsDisplayWidth setting in the
dataset column itself. It doesn't have any built-in mechanism to store the
run-time values, though it probably wouldn't be too hard for you to make a
descendant that would do that.

>seems something will be told about IBO with kylix in the IBO
>conference, but I'm not able to join. so can anyone tell me about the
>status of kylix/apache dso support in IBO? there's no eval kit for
>kylix.

If you join the IBO Kylix beta, you can have the code for
evaluation. Write to me privately if you are interested. Apache
support? what did you have in mind? IBO are database components.

Helen