Hi,<BR><BR>I have been experimenting for the first time with SqlTransactions, and it seems to me that an SQL DELETE which tries to delete a row that doesn&#039;t exist will cause the transaction to do a rollback, but an SQL UPDATE that tries to update data that doesn&#039;t exist does NOT cause a rollback.<BR><BR>I&#039;m curious as to why this should be. Is there a list anywhere of exactly what will trigger a transaction to do a rollback, and what won&#039;t? Is there a way of controlling this? <BR><BR>Thanks,<BR><BR>JON