I noticed that you always mention STORED PROCEDURE when talking about data manipulation. Can you explore more on this issue?
Create one SP per project?
Create one SP per table?
Create one SP per table & type of operation (Select/Insert/update/delete)?
Do you create a parameter for every field?
What about if the table contains a lot of fields?
How practical do you think it is using SP?


>Nabil,
>
>That will work, however I wouldn't do it that way because of the fact that it requires two round-trip calls to the server. Instead, either send both queries at the same time (your Sql string will contain both queries in it) or call a Stored Procedure that returns both tables (that is the way that I would do it).
>
>~~Bonnie
>
>
>>I created a typed dataset which consist of a parent table,child table, and one to many relation.
>>
>>The mechanism I'm following to retrieve the data of both tables is:
>>1- Assign the parent's parameters values.
>>2- Fill parent table.
>>3- Assign the child's parameters values.
>>4- Fill child table.
>>
>>Is that ok, or there is a better approach?