Read/Write Data-Binding & StoredProcedures

[Guest]

I'm trying to understand the most "elegant" way - the way that ASP.NET or ADO
would suggest handling the back-and-forth between a Web Form and the
database, when the data only get out of and into the database through Stored
Procedures.

Most of the samples I've seen make it LOOK very easy to use data binding
because the data are bound directly to columns in tables. But realistically,
do people really do this? If I have Stored Procedures to handle
INSERT/UPDATEs, DELETEs, etc., I'd love to see an example of how to still
take advantage of data-binding functionality instead of what I'm doing now -
which is programatically populating text boxes myself and then
programatically building SQL StoredProcedure calls to write data back.

Any help and samples much appreciated!

Alex

 

[Kevin Yu [MSFT]]

Hi Alex,

In ASP.NET 2.0, you can take the advantages of data-binding by binding to
data sources on a webform. Here are some samples of how these are done in
MSDN.

http://msdn2.microsoft.com/en-us/library/ms228089.aspx
http://msdn2.microsoft.com/en-us/library/ms178361.aspx
http://msdn2.microsoft.com/en-us/library/6759sth4.aspx

HTH.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)