Nelson,
Set implicit transactions is generally a call made by whatever client you are using. ADO does this automatically whenever you do a oConn.BeginTrans(). My guess is that the remote views you are using are doing this. It should be pretty easy to check

1. Create an updateable remote view.

2. Turn your profiler/trace on and
3. Make an update
4. See what gets sent to SQL Server.
5. I dont think that you will be able to turn this particular "feature" off.

Rodman