>Ken,
>I agree with the design to break the extra fields out but this isn't an example of what I was saying. If the view were designed to update both tables and you appended a record to the parent table and it wasn't a doomahickey, then you would get an extra record in the doomahickey extra information table and not need one.

right - I pointed this out in another post somewherealong the line :-)


>However, since you don't use views in this way, you wouldn't have to worry about this in the first place. You would just have conditional code in the AddUpdateDeleteInventoryItem SP that checked to see if the item was a doomahickey and if it was, insert a new record into the child table.

right again ... (or in front end code or through differnt SPT cursors depending on situation) - thus at least one example of another method's superiority over RV! - IMMESLAHO - that's " In My Most Ever So Lowly and Humble Opinion" lest I be accused once again of stating generalized absolutes. 8-D