I'm not sure what you saw in the past. Starting a SQL Server transaction does not "protect the data." Locks protect the data and the presence or absence of a transaction determines the length of time that the locks are held.

You should be able to see this. Start the transaction and modify a row w/o commiting the transaction. If you try to modify the same row on a different connection, SQL Server will block the modification until the first transaction is terminated - causing the lock to be removed.

-Mike

>Hello, everyone
>
>I have a very annoying problem, which started immediately after installing SQLServerSP2, but I'm not sure is related.
>
>I use remote views in my app. All the views are sharing the same connection. Till yesterday, if I USE a remote view, get the connection handle with CURSORGETPROP function, SQLEXEC(handle,'BEGIN TRANSACTION'), that table was protected from other users. In another session of VFP or in an AccessXP project, I wasn't able to open the table and mess with it, until the transaction was commited or rolled back.
>
>Now I am able to trash completely the table (deleting all the records) and the transaction doesn't has nothing to say. It even returns 1 at 'COMMIT TRANSACTION'!
>
>Does anyone know what's happening?
>
>Maybe not related, but even so: I saw this behaviour before, but very seldom, only on some remote views I've modified in ViewDesigner. I deleted and recreated them and they worked ok afterwards. Now all of them have the same problem, no matter the app, no matter the database, no matter the SQL Server database.