My first question that springs to mind is why mix VB6 and .NET, Why not
develop your VB6 components in .NET?
Pros of using stored procedures
====================
Less chance of the application being open to SQLInjection hacks.
Developer (front end) does not need to know the structure of the database
Developer (back end, DBA) can lock down access to DB items = more secure DB
Complexity of deployment
=================
You will only need to adjust your stored procedures if you have released
them containing bugs, and I'm sure your DBA doesn't do that.
I'm sure there's a lot more to say on this subject, but right now, off the
top of my head the above is what springs to mind. Oh yes, this applies to ALL
dev languages, not just VB6.
--
Of all words of tongue and pen, the saddest are: "It might have been"
Bill.Richards @ greyskin .co .uk
http://greyskin.co.uk
"scott" wrote:
Hi,
Just wondering what sort of problems and advantages people have found using
stored procedures. I have an app developed in VB6 & VB.NET and our
developers are starting to re-write some of the code in stored procedures
(im advocating encryption of them). When deploying an application however
stored procedure seem to add another level of complexity to installation. In
future we also plan to have an basic ASP app with some of the functionality
of the VB app.
What are the pros and cons of using stored procedures in the situation?
PRO
- can call same stored procedure for ASP pages which saves us writing again
CON
- more complex deployment (i.e sending a bug fix will involve shipping DLL
and SQL script for stored procedure).
Thanks for any input
Scott
pros and cons of using stored procedures for VB app ?
