Paul,

Dependencies are not particularly reliable in SQL Server 2000 and are fairly meaningless. Your problem of an UPDATE causing a row to be deleted can happen if there is an UPDATE trigger on the ShoppingCart table. It is also possible that the code that implements RunCommand is deleting the record.

Immediately after executing the RunCommand, check the Process Info in Enterprise Manager (EM..[INSTANCE]..Management..Current Activity..Process Info). It will show you the last T-SQL command that was executed which will show what the RunCommand() method is actually sending to SQL Server.

>The first 2 commands work as expected. The third command actually deletes the record it should be updating.
>

>RunCommand("update product set SKU = " + Common.SQuote(Sku) + " where ProductID = " + ProductID);
>RunCommand("update Orders_ShoppingCart set OrderedProductSKU = replace(OrderedProductSKU," + Common.SQuote(OldSku) + ","+Common.SQuote(Sku)+") where ProductID = " + ProductID);
>RunCommand("update ShoppingCart set ProductSKU = replace(ProductSKU," + Common.SQuote(OldSku) + ","+Common.SQuote(Sku)+") where ProductID = " + ProductID);
>

>
>I am new to SQL Server and I am using a database that I purchased for an online store.
>
>Anyway, I started playing around in Enterprise Manager and I chose to Display Dependancies.
>
>I noticed that Product doesn't have any dependencies, Orders_ShoppingCart is dependant on Orders, and ShoppingCart is dependant on Product.
>
>Is the fact, that ShoppingCart is dependant on Product and that I changed Product first, the reason?
>
>If this is the case is there a way to remove the dependency and then make the updates and then replace the dependency. I guess I don't understand what a dependency is for.
>
>Thank you,
>Paul