DevForce Community Forum : Link to SQL vs. Stored Procedures http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : Link to SQL vs. Stored Procedures Fri, 10 Apr 2026 22:31:30 -700 Tue, 28 Jan 2014 18:16:23 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=4642 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Link to SQL vs. Stored Procedures : Hi Bill,I would say that as a... http://www.ideablade.com/forum/forum_posts.asp?TID=4642&PID=17344#17344 Author: DenisK
Subject: 4642
Posted: 28-Jan-2014 at 6:16pm

Hi Bill,

I would say that as a rule of thumb, if the entities you're inserting, updating or deleting are not required on the client, you can safely use Stored Procs.
]]> Tue, 28 Jan 2014 18:16:23 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=4642&PID=17344#17344 Link to SQL vs. Stored Procedures : up to this point in my upgrading... http://www.ideablade.com/forum/forum_posts.asp?TID=4642&PID=17339#17339 Author: BillG
Subject: 4642
Posted: 26-Jan-2014 at 12:10pm

up to this point in my upgrading a vb app, I have been using Objects to work from my data. Now i am coming across some vb code that relies heavily on SQL for iserrts, updates, and deletes. I am looking for some recommendations here. Should i continue using objects and look through collections for inserting, update, and deleting moderate amounts of data or should i use Link to SQL or even Stored Procedures? What advice could you give me here?

Bill

]]> Sun, 26 Jan 2014 12:10:45 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=4642&PID=17339#17339