Last post Feb 25, 2012 02:06 AM by Ken Tucker
Feb 24, 2012 06:01 PM|SandpointGuy|LINK
Im taking a Sql Server/.NET Winforms app and converting it to asp.net for the customer. The original developer uses strongly-typed Visual Datasets with all the DataAdapter, .Fill, .Update, etc functionality. My app is using custom collections with a data
access layer build on top on Entlib. Im pretty much able to follow what the original developer did, but Im not very familiar with strongly-type datasets.
Im updating the tables in the same manner as the webform app, so I am planning to run the asp.net and the winform app side-by-side until the customer is comfortable with a full cut-over.
Here is my question: if I make changes to the structure of a table - not removing columns or renaming columns, but adding new columns, does that have any effect on the dataset and its built-in functionality? Put another way, if its a nullable column, will
the dataset ignore it?
Feb 25, 2012 02:06 AM|Ken Tucker|LINK
Yes if they are nullable columns the dataset should be able to safely ignore it. I wouild check the select statement to make sure select statement names each column instead of using select *