>Although I am successfully using Remote Views on separate tables, I find TABLEUPDATE() a bit cranky and, at times leaves me scratching my head - try these two instances:
>
>(1): TABLEUPDATE(.T.) fails, and AERROR[1,2] returns the cryptic message "Incorrect syntax near the keyword 'UPDATE'" - while AERROR[2,2] tells me "Incorrect syntax near 'LIKE'" - these from an OBDC connectivity error 1526. Only 1 non-primary field was modified. All the usual DBSETPROP() settings are set correctly as far as I can tell. Since TABLEUPDATE() operates behind the scenes, is it telling me to give up Remote Views and use SPT functions instead?
>
>(2): Same View, different day: Memo fields are modified, and TABLEUPDATE(.T.) returns .T. for a small result set with table buffering on. Great, the UPDATE was successful - right? Wrong, the View is refreshed and none of the Memo field changes were sent. I've checked (and unchecked) the Fetch Memo. Veried and re-checked all settings, Updatable fields, etc. Why does TABLEUPDATE() tell me the Update is successful, when obviously that's not true?


Hi Brian,

I had the same problem you mention in point (1) about two weeks ago. I was using SQL Server 6.0 with the latest SQL Server drivers from Microsoft. The problem occurred when updating a memo field using a parameterised remote view. The remote view's update method was set to 'Key Fields and Modified'. This problem only started happening after I had installed the latest SQL Server ODBC drivers from Microsoft. The solution was to revert to the older set of SQL Server drivers (I can't remember the exact version - 3 something I think). Another solution may have been to use SQL Server 6.5 - I'll find out in a week or so when I get my hands on 6.5.

Regards,
Jamie.