Thanks for the reply.
I lose the connection because I want to :-) , by stopping the server or release the connection. I mean that I want to handle these errors and I want to know the best solution for it. It would be nice if I could reconnect with SQLCONNECT() and set the "ConnectHandle" property of the remote view cursor to the new handle, but I can't.


>Are you losing the connection to the back end because you're working on a WAN? or are you releasing the connection handle after accessing the view?
>
>An alternative approach could be to bring the row down to your machine, then edit it, then re-connect and send the data back again. If you use stored procedures to process all remote data transactions, then you can implement security based on these which you can't do in a remote view arrangement.
>
>Regards
>Simon