Arthur Fuller
fuller.artful at gmail.com
Sat Nov 13 13:01:54 CST 2010
Assuming that you are using an ADP rather than a standard Access file, the way to go is to invoke stored procedures for just about everything. The problem with dynamic SQL is that there is no way for the engine to optimize and store the navigation-path; hence, sprocs are almost always better, and in addition not prone to SQL injection. But I also realize that in some circumstances this is not a reasonable or feasible approch, so take my advice with a grain of salt. But if and when I can, I will always go with the ADP+Sprocs approach. A. On Sat, Nov 13, 2010 at 12:33 PM, Mark Simms <marksimms at verizon.net> wrote: > Isn't the larger issue whether or not a stored procedure is called vs. > dynamic SQL ? > Also, what about ODBC vs. a native driver ? > I thought both of these were hugely important, no ? >