Devart Forums

I am just converting an application from IBX to IbDAC.
There's a Grid-component that uses the datatype property of a field to determine what's in the field -> how to display the data.

Depending on the type it displays:
*) strings (ftString, ftWideString) are simply displayed
*) for Text-Blobs (ftMemo) a symbol for Blob-Text is displayed
*) normal Blobs (ftBlob) are displayed as graphic

Works fine with IBX (tested on same database & table), but IBDac doesn't return ftMemo for Text-Blobs. It always returns ftBlob for both Blob-types (binary and text).

Help!

Hello,

You should set the TIBCConnection.Options.EnableMemos option to True. This option is used to enable creating TMemoField and TWideMemoField for BLOB fields with subtype 1.

AndreyZ wrote:You should set the TIBCConnection.Options.EnableMemos option to True. This option is used to enable creating TMemoField and TWideMemoField for BLOB fields with subtype 1.

Super, that solved the problem
Thanks!!!

One question remains: If this property is there to support creating Text-Blobs, why does it affect READING from an existing table?

When you are opening an existing table, the dataset component creates fields for BLOB TEXT columns. Depending on the EnableMemos option value, it will be either TBlobField (ftBlob) or TMemoField (ftMemo).

AndreyZ wrote:When you are opening an existing table, the dataset component creates fields for BLOB TEXT columns. Depending on the EnableMemos option value, it will be either TBlobField (ftBlob) or TMemoField (ftMemo).

Maybe consider changing the default settings.
I guess most developers expect a Blob-Field with Subtype Text to result in a Memo-Field.
(For me the problem is solved now, I'm just thinking about future customers)

We will investigate this question. As soon as we get any results, we will let you know.