Hey Jason. I can understand the memory concerns about storing the data in arrays etc. But, the temp-table database solution sounds a little kludgey to me. How many items will they really be adding before saving? If it's so much data that there is actually a client memory concern, then I would argue that the bigger concern is with the user losing an hour of entry when his/her PC shuts off! Could you enforce a save-per-fifty entry policy by triggering a Save function when a counter reaches a certain point?

I think the database approach will work, it's just one of those span-architecture-layer approaches that I like to avoid.

HTH.

>Looking to get some input from others who have already done similar things. I have a form with a tab control on it. On these tabs there are multiple TreeView objects. When the user clicks on a node item the corresponding data is called from SQL server and displayed in etxt boxes. The problem I am having is how to store the data when new items are added. I don't want the new items to be added until the user clicks save so I have to temporarily store the data somewhere first. Originally I was using dynamic arrays to store all of the data but I figured these would amass in size at some point and not be efficient. I'm worried that using arrays will suck up too much memory on the client. Alternatively, I could use the arrays to only store the new items but I haven't tried that yet. So now I am thinking about using a temporary table on the server to store the new records, then when the user clikcs save, itterate through the table and do batch transactions with stored procedures for the
>updates. So if you have an opinion or an idea around this I'd love to hear it. Thanks.