Hi Roy

<< Then is there a reason for "because I also store the text as plain text in another field"? Just curious >>

The current version of my app uses DBISAM and the data is stored as RTF in a BLOB field.  Every now and then for whatever reason a user may need to repair their database due to data corruption. In some of those cases, when the BLOB field was displayed in the app the RTF code was visible and the text was truncated.  

The PlainText field was introduced as a sort of backup field so that the text could be restored, minus the formatting.  This has been carried over to the EDB version of the app.  It now looks like it will serve more than one purpose now.

= Steve

<< My suggestion applies only to a "plain text" RTF document, not to a
binary format of course. The binary wouldn't be searchable in EDB
either. >>

Naturally.

= Steve

I have TRichView working with EDB.  I have it stored in a single CLOB field and it is searchable.

-  If using Unicode, make sure "everything" is set for unicode.

-  Make sure that all TRichview settings are set to use RTF, not RVF.

-  Store the data in a CLOB.

-  To be able to search the data, you must set up a separate text filter to filter out the RTF codes (look up text filters in help).  Look in the binaries section for Roy Lamberts RTF filter.  I think there is a modifed version of this but I could not get it to work correctly so I've been using Roy's original one.  I can't remember what it is called.... stripRTF maybe but I'm not sure.

And, in order to support searching, you must store it in a CLOB.  This means that you must change the setting in TRichView to save images as text.  This can cause VERY VERY SLOW load times if images are present.  If you need to store images in the RTF document, then this could be a dealbreaker.  So far I have not figured out a way to get around this so for now we do not allow images in this field.

It was tricky getting it all to work, but it can be done.

Dale

<< I have TRichView working with EDB.  I have it stored in a single CLOB field and it is searchable.

-  If using Unicode, make sure "everything" is set for unicode.

-  Make sure that all TRichview settings are set to use RTF, not RVF.

-  Store the data in a CLOB.

-  To be able to search the data, you must set up a separate text filter to filter out the RTF codes (look up text filters in help).  Look in the binaries section for Roy Lamberts RTF filter.  I think there is a modifed version of this but I could not get it to work correctly so I've been using Roy's original one.  I can't remember what it is called.... stripRTF maybe but I'm not sure.

And, in order to support searching, you must store it in a CLOB.  This means that you must change the setting in TRichView to save images as text.  This can cause VERY VERY SLOW load times if images are present.  If you need to store images in the RTF document, then this could be a dealbreaker.  So far I have not figured out a way to get around this so for now we do not allow images in this field.

It was tricky getting it all to work, but it can be done. >>

Thanks Dale. I really appreciate it.

= Steve