R
Ron L
I have an existing ASP/ MSSQL project that we are looking at migrating to
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data returned
depending on the user's permission to certain classes of data we hava all
access implemented via stored procedures. Another reason for using SPs is
that certain tables have a requirement to keep track of who made changes,
what the change was (old and new data), and when the change happened. Given
these requirements, it appears to me that adding a web service simply
inserts another layer between the user and the database, and one that is
going to require that I define a Command object for each stored procedure
call. Are there advantages that I am not seeing, or am I better off just
having my application create the necessary data objects that directly query
the database?
TIA
Ron L
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data returned
depending on the user's permission to certain classes of data we hava all
access implemented via stored procedures. Another reason for using SPs is
that certain tables have a requirement to keep track of who made changes,
what the change was (old and new data), and when the change happened. Given
these requirements, it appears to me that adding a web service simply
inserts another layer between the user and the database, and one that is
going to require that I define a Command object for each stored procedure
call. Are there advantages that I am not seeing, or am I better off just
having my application create the necessary data objects that directly query
the database?
TIA
Ron L