Problem adding to a memo field

[Raymond Lyons]

I have discovered that using:

If parentform:conv_log.value<>""
    parentform:conv_log.value=D_T_stamp+rtrim(v_User_first_L_Int)+":  "+new_text+crlf(2)+conv_log.value 
    else
    parentform:conv_log.value=D_T_stamp+rtrim(v_User_first_L_Int)+":  "+new_text
end if

where "new_text" is text to be added (coming from an xdialog) to an existing memo field works perfectly until the existing text (conv_log.value) is about 987 characters or so in length. At that point, even when just adding the word "test" I get a "field Types don't match" error message that can't be quite right (see screen shot) if for no other reason that it works until the existing text is long.

I tried using

fld = tbl.field_get("conv_log")
old_txt = fld.value_get()

instead of the conv_log.value but it made no difference. Also tried conv_log.text, again no difference.

Any suggestions?

Ray

[Tim Kiebert]

Re: Problem adding to a memo field

I remember something like this coming up in the past so a search should bring it up. Try using conv_log.text instead. I think the type mismatch maybe a result of a text variable going over a certain size getting treated as a blob, but that is just a guess.

[Raymond Lyons]

Re: Problem adding to a memo field

I remember something like this coming up in the past so a search should bring it up. Try using conv_log.text instead. I think the type mismatch maybe a result of a text variable going over a certain size getting treated as a blob, but that is just a guess.

Tim,

I don't doubt that there may be something in past posts but if there is I have not been able to find anything that addresses this particular issue. And note that I have "tried conv_log.text, again no difference."

I suppose it is a matter of the size of the existing text going into a variable, but so far I have not seen a way around this short of writing the existing text to a temp text file and then writing it back in. Maybe using a blob somehow? Or??

Ray

[Peter.Greulich]

Re: Problem adding to a memo field

Try:
.MEMO_READ_FROM_FILE()
.MEMO_WRITE_TO_FILE()

BTW: I'm pretty sure variables can hold more than 987 characters - at least they could in v.5.

[Tom Cone Jr]

Re: Problem adding to a memo field

Raymond, I'm curious about this and will be happy to work on it. Do you have any convenient sample data that could be used to assure that what I'm work on will parallel yours ?

Later:

Here's an example that is not having the problem you experienced. Perhaps it will help you get past the current stumbling block. You will notice that my code is not trying to read the value or text properties of the objects in the form layout (like you were doing). Instead, it directly manipulates the table beneath the form. My code does not write the new string back to the object displaying the memo field, either. It talks exclusively to the table supporting the form, not the objects in the form.

[Tim Kiebert]

Re: Problem adding to a memo field

Ray, I found the thread I was thinking of. Trouble is the suggestion I made was what was causing the problem that started that thread. Sorry for the bad 'help' :o

[Raymond Lyons]

Re: Problem adding to a memo field

....Here's an example that is not having the problem you experienced. Perhaps it will help you get past the current stumbling block. You will notice that my code is not trying to read the value or text properties of the objects in the form layout (like you were doing). Instead, it directly manipulates the table beneath the form. My code does not write the new string back to the object displaying the memo field, either. It talks exclusively to the table supporting the form, not the objects in the form.

Tom,

Based on further testing with your example and my live Db example, the real key is to write the new string back the way you suggested, via
tbl.change_begin()
tbl.change_end()
rather than using the form objects--though I would still be curious about why using the form objects work until the write string reaches a certain size.

FYI, it also turns out that getting the current memo value via something like:
fld = tbl.field_get("conv_log")
old_txt = fld.value_get()
versus merely parentform:conv_log.value does not matter. Either way works, though I wonder if the form object would continue to work as the string gets longer. Anyway, it seems to just matter how one writes back the new, larger string.

Thanks for the help.

Ray