>
>I'm exploring Microsoft sample code.  This is a master/detail scenario with
>two SqlDataSources.  The master table shows Northwind.Customers data.  In the
>detail table, I can massage a row of data selected from the master table.
>
>In the SqlDataSource code that handles the "detail" part, I see a mile-long
><UpdateParameters> list:
>
><UpdateParameters>
>  <asp:Parameter Name="CompanyName" Type="String" />
>  <asp:Parameter Name="ContactName" Type="String" />
>  ...
></UpdateParameters>
>
>If I delete the list, the program works just as well.
>
>- Why is that?
>- What is the purpose of the list?
>
>Thank you.
>
>
>

>
>I'm exploring Microsoft sample code.  This is a master/detail scenario with
>two SqlDataSources.  The master table shows Northwind.Customers data.  In the
>detail table, I can massage a row of data selected from the master table.
>
>In the SqlDataSource code that handles the "detail" part, I see a mile-long
><UpdateParameters> list:
>
><UpdateParameters>
>  <asp:Parameter Name="CompanyName" Type="String" />
>  <asp:Parameter Name="ContactName" Type="String" />
>  ...
></UpdateParameters>
>
>If I delete the list, the program works just as well.
>
>- Why is that?
>- What is the purpose of the list?
>
>Thank you.
>
>
>