wb Larry. You can be sure ... in the long term I will certainly optimize the database structure. But since we're talking about a productive system made up of 13 million lines of (VB6) code, I can't do that on the fly ... as much as I would like. If I had a performance problem adding, querying, deleting or editing rows in such monster tables, I would have no other choice. However, all of these processes take place in an absolutely acceptable time. Only the creation of the necessary SQL statements with the CommandBuilder takes an incomprehensible amount of time and I cannot think of any reasonable reason why this should be the case. And please ... don't start a pointless "C#" vs "VB.net" discussion. As long as both languages lead to the same IL and remain translatable into the other, that's only a matter of taste ;-)