>>I like to use populate in this cases, and I think I would separate the work for each list
>>
>>populateSource()
>>populateDestination()
>>getSourceItems()
>>getDestinationItems()
>
>+ 2 more methods Populate() and GetItems() since these methods will call generic method with object reference?
>
>Sounds interesting, may be I should re-design. (In the meantime I just finished adding new methods as Boris proposed) but haven't coded them yet.
>
>Let's see what Boris think - I like your idea better, actually.
:-)
Original question was to populate both source and destination in one method :-)
But I like this more , you are more flexible :-)
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.