Re: Execute Stored Procedure Error
From: Virginia Kirkendall (vkirkendall_at_hotmail.com)
Date: 06/01/04
- Previous message: Tom Kelleher: "Connection.Errors only contains ONE error"
- Messages sorted by: [ date ] [ thread ]
Date: 1 Jun 2004 13:09:05 -0700
"Val Mazur" <group51a@hotmail.com> wrote in message news:<e5MrPaSREHA.2216@TK2MSFTNGP12.phx.gbl>...
> Hi Virginia,
>
> I probably did not understand problem correctly. I understood that you need
> to past just a some sort of a LIKE condition. Since you need to pass complex
> condition, the I do not see good reason to use SP here. From one point SP
> looks better, but you will not gain anything and will add a security issues
> into your application. Since your query inside of SP is built dynamically,
> your query inside of SP will be re-compiled each time when you run this SP.
> No performance advantage in this case. But building SQL statement
> dynamically inside of the application, would allow you to control what your
> application injects into this SQL statement. Of course, if you are not
> concerned about security, then you could leave statement inside of SP.
>
Yes...I have been finding that you are correct w/regards to dynamic
SQL inside an SP. I've been building the criteria strings & setting
up ADO recordsets with better results. Thanks for your response to my
issue.
- Previous message: Tom Kelleher: "Connection.Errors only contains ONE error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
