Vlad,

> > > If SP has outputs - do SELECT else do EXECUTE. What is wrong with

it ?

> >
> >
> > A procedure can have output parameters and produce output
> > without having a SUSPEND. Such a procedure returns results
> > when called with EXECUTE and returns NO ROWS when called
> > with SELECT.
>
> This is develore's mistake - write procedure without SUSPEND
> and call it with SELECT. This "problem" is like a "problem" with
> FOR SELECT INTO when variable not change it's value if resultset
> is empty

That is NOT the problem that's being discussed.

The problem is "how to know if you should use SELECT or EXECUTE
if you don't know anything about the procedure".

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com