I was having the same problem with a system I'm porting from BDE to IBO. It
was really a subtype problem. It was set to 2 and when I changed it to 1
everything worked. The "funny" thing is that with BDE it always worked,
even with subtype 2, so I think IBO does some diferent treatment based on
the subtype... Jason ?

[]s

Carlos
WarmBoot Informatica - http://www.warmboot.com.br
Interbase-BR - http://www.interbase-br.com

HB> At 03:52 PM 06-02-01 -0600, you wrote:

>>Because it was a typo :o(. Here is the real value:
>>
>>NOTES BLOB sub_type 2 segment size 128
>>
>>Do you have any suggestions as to what the real problem might be?

HB> Here is your original statement:

HB> "I am receiving the message in the subject line when I attempt to display a
HB> memo field using a TDBMemo control. Here is how my memo is defined in my
HB> table:
HB> NOTES BLOB sub_type 2 segment size 1[28]"

HB> You are trying to put a binary blob into a memo control - it won't
HB> work. TDBMemo needs a text blob. I suspect what is happening here is that
HB> the client is asking for some special stream format that is "text in a
HB> binary representation". Because you have not defined a Blob filter that
HB> fits these requirements, it's just coming back and saying it can't
HB> represent it.

HB> Change the definition to sub_type 1 or 0, or just drop the sub_type
HB> altogether and IB will just store whatever it receives (it defaults to 0,
HB> unstructured).

HB> Another thing is - if you are using the TIB_ native IBO data access
HB> objects, TDBMemo won't work with them. You need a TIB_Memo.


HB> Helen


HB> All for Open and Open for All
HB> InterBase Developer Initiative · http://www.interbase2000.org
HB> _______________________________________________________