Hi John -

Thanks for the ideas. Guess I'll have to add ADO to my current list of items to learn.

I think I am on the same path you are suggesting. Yesterday I built a generic framework using the Strategy Pattern (thanks Markus!) so that no matter what type of data I am udating, it just calls the same type of object. Now today I will approach the actual code.

Thanks!
~ ellen


>Whenever you make a change to something, have a collection class of some sort get populated. Then, when you need to go through the update process, pass the collection. Have the update process iterate through the collection. What information is contained in the collection depends on your situation. If you are using ADO, the collection could be an array of ADO Recordsets. If you use other data access strategies, the task gets a bit more difficult, but it can be done. This is why ADO is nice, because it is a set of true objects that can be passed around.