Hi,

Since that discussion in Thread #245948, I rtrimed by varchar2 key field in Oracle. Since I don't want to introduce trailing spaces into the field in Oracle, I changed the VFP remote view datatype for the key field to "M". I have an vfp algorithm to generate the varchar2 key. I added a non-updatable field to the remote view using substr:

SELECT Plsprj.*, substr(Plsprj.proj_no,1,8) as proj_no_display

On my data entry screen, I have a disabled text box that uses proj_no_display as the control source.

The best solution is a numeric key field, but if you are stuck with a varchar2 key field, a memo field in your remote view works fine.

Good luck,

Paul


>>>Has anyone came up with a fix for the problem with the VARCHAR2 data types in Oracle. Remote Views in VFP will always pad the field with spaces. I have several tables that have the key field as a VARCHAR2 in Oracle. I can not use remote views to update the Oracle data because '123' and '123 ' don't match! I can use SPT to update the tables and ADO seems to work but I really want to use remote views.
>>>
>>>-David-
>>
>>Then you would have to change the view's update type to Key Fields only. This is a known issue with this data type in Oracle. This was discussed in Thread #245948 dated July 25 in the Client/Server category.
>
>I checked out the thread, thanks. My problem is that the Key Field is a varchar2 data type. The discussion in this thread addressed options where non-key fields were varchar2's.