OK.. not really sure how to ask this so I will explain what I'm trying and hopefully get an answer.
I am writing an application that will allow me to move and/or update data. This will be a large application that will be used by no less than 100 users accessing around 80 PCs throughout the day.
I'm pretty well versed in 'data-bound' controls, but that's not necessarily the best solution for this situation. In most instances, I will have the user looking at a table and selecting items (could be any number of them) and moving the data, not the records, to another 'table' in SQL. I would prefer, if possible to keep the information in RAM until the records are ready to write to the new datatable... any suggestions on how I would do this?