>>So, should I go back to Dictionary? Usually the number of columns for table no more than 250 columns.
>
>I would say yes. Your situation is what a Dictionary is designed for (quick lookup based off of a key), and the overhead to create it will probably be more than offset by the time it saves. I didn't see any compelling argument against doing so.

Thanks again. Luckily I did post my latest changes last night, so I just grabbed them back. I am only going to adjust the AddTableSchema method using your suggestion instead of looping through each row.