Subject | Re: [IBO] TIB_Memo |
---|---|
Author | georgethenorge |
Post date | 2004-06-14T05:08:49Z |
Thanks for letting me know what is going on under the hood. I have
now changed refresh action to raKeepDataPos. AutoDisplay was already
True.
The problem is better but not all the way solved. If I add text to an
empty blob, it disappears when I hit the save button. Changing text,
however, works just fine.
George
now changed refresh action to raKeepDataPos. AutoDisplay was already
True.
The problem is better but not all the way solved. If I add text to an
empty blob, it disappears when I hit the save button. Changing text,
however, works just fine.
George
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> George,
>
> At 02:39 PM 13/06/2004 +0000, you wrote:
> >I am having trouble with a TIB_Memo component. It doesn't save the
> >data correctly. If I type in text, then hit the SAVE check mark,
the
> >data disappears. If I put the cursor on another field first, then
it
> >disappears, but reappears when I reopen the form to that same
record.
>
> Assuming you're using AutoCommit and the TIB_Memo is bound to a
blob, this
> is the expected behaviour. Blobs are not stored on the database
> record. When you "edit" a blob, it is never actually edited. The
new
> version of the contents is stored as a completely new object on the
server,
> with a new Blob_ID.
>
> When the modified record is refreshed after the commit, the dataset
buffer
> only has the new blob_id. Blob data is fetched "on demand". After
the
> refresh, when you focus again on the same record, the dataset
fetches the
> blob data for you.
>
> You should be able to get the new blob data after the commit by
setting the
> RefreshAction of the dataset to raKeepDataPos and the AutoDisplay
property
> of the TIB_Memo to True (quite costly if the blobs are big and the
dataset
> is being navigated by scrolling) or by keeping it false and
simulating an
> Enter or double-click when the row or the control gets the focus.
>
> Helen