I think Rick's comment: "Doesn't .Equals check memory address" maybe the cause of my current problems, and Chrissie1's solution may not work either. I will restate the problem with an simple shopping cart example that allows the user to order various parts. This is not what the real application does, but I think the shopping cart example is one everyone can relate to.
I have an object named oPart.
It has the properties of: ItemNum, PartName, Length, and Depth.
As parts are chosen, they are placed in a collection named cPartsList.
Each time the user makes a change to their order, the old cPartList is destroyed and a new one is created.
Right before the old list is destroyed, a copy is created as cPartsList_Old.
After the new list is populated, I want to compare the two list to find parts that have been added or deleted.
Using Object.Equals fails to find any matching parts.
Question: What is the best way to finding matching parts in these two collections?
--Rob