Leland,

I'm looking for a way to break the link because of the buffering. I want the "cursor" that's created by the SqlExec() to act like a cursor! I don't want to have to issue a TABLEUPDATE() after each REPLACE or UPDATE statement.

With regards to the possibility of a recurring SQLEXEC() with every row change, I can't say difinitivly, but I can say that there's one hell of a lot of I/O on my network when I'm running SQL Passthrough.

Regards,
Thom C.

>>By the way, is there a potential problem in using remove view when working with a non-native back-end server like MSSQL or Postgres? The fact that you feel a need to be unlinked from the back-end server worries me a little. Is it possible that you are unlinked from the back-end, but because VFP sets the buffering to optomistic 3, VFP may be issuing a SQLexec() everytime you advance to a new row. I think a view is exactly like SQL pass through, except VFP does a lot of the work for you in the background like identifying records to be updated and inserted, prasing the commands and sending the command to the back-end server.