Whatever method you use is going to go through the SQL Native Client. None are immune to time out errors, blocking, port unavailable, etc. Here's a from-memory list of items to check on:

1) buffermode 3 rather than 5 updates
2) set SQL Server to row-only locking
3) if you are using a lot of lookups, don't reuse connections
4) set RCSI on so that lookups and report queries can proceed against rows that are locked by another user in a transaction
5) make additional ports available to SQL Server
6) fast server, lots of memory

You can Google on items 2,4 and 5 and get directions on how to do it from the horse's mouth, so-to-speak.

Hank

>I have been using remote views is this a stable way to go? I am getting time out issues, etc. Is there another way to update Sql Server then using remote views, if so point me in the direction I need to go, or a simple sample if there is one so I can see what is going on.
>
>Thanks