SQL Datasource or ADO.NET Code ?

[Bubsa]

Afternoon Team

I am slightly confused about the difference and advantages of the differnet methods above. Basically I have been tasked with creating a web application for a quote mangement system that currently resides on VB6 and Access database.

Now I have never used ASP.NET before but am skilled with SQL I have transfered the data from access to SQL and am halfway through designing the front end of the application when accessing the data I have been using gridviews and detailsviews and writing SQL queries this seems to be working fine. The issue I have is I now need to use a stored procedure to update the Quote and Item table at the same time.

I have been trying to research exactly how to do this and have been advised on another site to to change my whole application into a 3 tier app and redo the connections using ado.net SQL commands please can someone expalin to me why? as ado.net seems a lot more complicated than the way I am currently doing this? is the performance that much better surely I can use a simple stored procedure the way I am doing things now in a detail or form view?

 

[baddos]

It's slower performance, but it's best practice design. Ideally there should be a middleware piece that handles the database calls.