My rule of thumb with stored procedures is to use them whenever you can.
The one place where they are not efficient or feasible to use is if you want
the benefits of search mode or any type of where clause manipulations.
stored procedures do not incorporate any where clause criteria inside of the
implementation. They just scan all records the SP produces and reduce them.
Also, it isn't possible to take advantage of some of the other enhanced
buffering capabilities of IBO like horizontal dataset refinement and
fetchwholerows=false.

There are some cases where I knew all the possible where clause options and
so I decided to make input parameters that would deliver them all. I had an
implementation of about 50 select statements or so where only one would be
executed depending on the values passed in. It works great.

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "jonathanmfreedman" <jonathanmfreedman@...>
To: <IBObjects@yahoogroups.com>
Sent: Thursday, May 09, 2002 5:13 PM
Subject: [IBO] stored procedures versus queries


> should i, if i am responsible for developing both the server database
> and the user interface, used stored procedures to select data for
> viewing, update data, and otherwise control all the transmission of
> data from the server to the client, and call them thru stored
> procedure objects instead of query objects?
>
> jon freedman
>