>>Hi Mark,
>>
>>I'm sending this to you, since I've seen you comment many times of VFP/Oracle issues.
>>
>>I am having problems with Oracle varchar2 fields in my remote views in vfp5.0. I did a UT search on "varchar2" and saw that others were having the same problem. Someone mentioned the KB q170129 article. One possible solution from the article was to "Change the data type of all Oracle varchar2 fields to VFP Memo". I tried this on one of my remote views. Insert and update seem to work fine.
>>
>>Is this mapping of varchar2 to memo the best way?
>>
>>Am I going to have any problems using memo fields as my data source for my text boxes?
>>
>>Any comments??
>>
>>Thanks in advance.
>>
>
>If that is your preference for handling this, I believe you will really need to use an edit box. If you use a textbox, all you will see in the control is the word memo and your users will have to either double-click or ctrl+pgdn in the control to bring up and edit window.
>
>I prefer the option to change the remote view update type to Key Fields only in order to avoid this problem.

You can use textboxes to bind to a memo field, but not directly. Instead of using ControlSource, you have to put code in lostfocus and refresh events like:

REfresh()
THIS.Value = ALLTRIM(MyView.MemoField) && Alltrim converts it to char

LostFocus()
REPLACE MyView.MemoField WITH THIS.Value