Ferrell,

If the table you're updating has a lot of rows and don't have an index on the key field(s) you're using to update the table that might be the problem. When you update a remote view, VFP just creates a SQL Update statement and sends it to the back end. If there's no index on the key you're using SQL Server will have to scan the entire table looking for records matching your key expression. If the table is large, that can take a long time.


>I synchronize data from Visual Fox Pro on a client machine to SQL Server on NT4.0. It seems when I have 3 or 4 records and try to save the changes in a remote view it hangs for a long period of time, but it will finally complete with out any appearant loss of data.
>
>Using this command line to save the changes:
> llRetVal = TABLEUPDATE(.T., .T., lcRVTable, 'arr_err')
>
>Where lcRVTable is the view name of the remote view and arr_err is not being populated nor is there any indication of a failure.
>
>Why does it hang for so long?
>
>Ferrell Willis
>fwillis@att.com