I have an application that contains multiple treeView objects. When the user clicks on a node, data is retrieved from the SQL server and diaplayed in appropraite objects for display. Right now (for simplicities sake to get the prototype working) if the user wants to edit an item (or add one), they click a button and a new form opens up to allow adding/editing. I do this because if they make a change on an node item on the original form, and then switch node items, the previous changes disappear unless I prompt for a save. I would prefer to allow the user to edit all over the place and add whatever and then hit the Save button once to process all changes. I started with dynamic arrays at first to store the data but this grew too cumbersome and I fgiured there had to be a better way. Right now I am toying with the idea of client side disconnected recordsets, but unfortunately I think this would bugger my identity seeds. Any suggestions about storing information temorarily on the client and then doing batch processing?