>>I saw that you had switched to ADO successfully, so maybe there is no need to pursue this. However, I have been supporting a large VFP / Sybase application that uses remote views for 8 years (SQLAW versions 6 - 9) with no problem. So there is no inherent problem with Sybase and VFP remote views. I always mark the PK column as updateable, so that by itself should not cause a problem.
>
>I ran into one problem in which an updateable Datetime column had a default value of CURRENT TIMESTAMP in the Sybase database. The VFP view always gave a conflict error on update, since Sybase was filling in the milliseconds column, but VFP only retrieves the whole minutes and seconds into the remote view's cursor. Curious whether anything like that could true in your app?
>
>Thank you for reply. I have tried updateable remote views to update other database like Access and VFP and it works fine with these except Sybase SQLAnywhere V5. I have tried about 3 different Sybase database same version and the problem is same. Finally, I solved it by using ADO. I have one sample/demo database and if you want to try I can send you by email.

Yes, I would be interested to see what is going on. I can receive attachments up to 10 megabytes. Send it to jeslater@comcast.net to avoid spam catchers.