Well in my VFP pos system I have an Inventory table that holds the model#, description, mfg, category ,etc. There is a child table that holds a record for each color/size/location matrix option which holds pricing information, quantities, and different sku numbers for each item.

The shopping cart structure is different. While it has a main table for description, model, etc. The child table for holding variants has a variety of ways it can show the variants. If they only want one record to list on the web with a drop down for color/size combinations they would only have one child record where 2 fields exist one for a list of color options, the other for a list of size options,delimited with comma's. In the pos system they might add a color, delete a color, change the name of a color, etc.

My thinking is it would be easier to delete the records in the shopping cart and then recreate the variant based on the children that now exist in the pos system.

I hope this clarifies, However, I'm sure it doesn't :-)

Which brings me to my original question. I don't think it would be *impossible* to "update" but there are quite a number of issues that will come into play. That is why I was asking if it's not a huge problem delete a bunch of records in SQL server this would difinitely be an easier option for me.

Thanks for your help,
Paul

>I still don't see why you can't just update the records. Can you post an example of your tables?
>
>>To clarify... I might have one record in a product table that is for a guitar and then there is a related 'variant' table that holds the sku number, color, etc for each modification of that guitar.
>>
>>If that one guitar changes I was going to delete the one record in the product table and possibly 10 records out of the variant table (for example) and then readd the one guitar and 10 variants. The other non-related records would not be deleted and readded.
>>
>>So what do you think now? Do you think this is acceptable?