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?



>I have a remote view to update Sybase SQL Anywhere version 5 database. The parent table has a valid primary key and I have selected the updateable field and primary key field and also Send SQL updates is checked. Now when i run the view and try to update the updateable field it gives me error Update confilct. There primary key in parent table is unique and there is no any primary key voilation. I have tried by using different Where SQL clause but no success. Please reply me if someone have some solution to update Sybase SQL Anywhere version 5 using vfp9.