I generally use passthrough for ad-hoc queries and remote views when I need to update the underlying table. If you make sure that the FetchSize of your view is -1 I think you'll find that you get speed that's almost identical to passthrough.

As for updating your tables, does TABLEUPDATE() return .F.? If so, you can use AERROR() to see what went wrong. You should also make sure that you've designated your key field(s) and which fields to update in your view definition and that your view is set to send SQL updates.

>Hi!
>I am looking for opinions on
>using...Remote Views in a DBC versus, Calling Stored procedures on a database or using SQL Passthrough queries to implement a backend for my 123 table application.
>
>I have done some testing and found SQL passthrough queries to be the fastest but they are of course more work.
>
>Also I found that the remote view's are fine but when you do a tableupdate() The changes are not in fact saved to the underlying table as I was told they would...
>
>I would also appreciate any references on this as I am trying to build a function library with select, update , delete ect,connect, functions for my application.
>
>Any tips or past experience would be great...
>
>Thanks All!