It's coupled somehow. If you put the column name in a string (untyped datasets) or if the dataset is strongly typed, it doesn't really matter. If you make a schema change, you'll have to modify the code either way. There are some places that tight coupling is needed and makes sense.


>I'm frankly puzzled about this one. As much as I love (and would love) to have intellisense on everything that resides in the database, to "strongly type" datasets assumes that you duplicate your datadictionary in your code no? Doesn't that increase coupling between two components (compiled code and data in the database) that we have worked very hard to de-couple?