> This doesn't make sense or I can't get it. I don't know what does isql
> have to do with the issue at hand and the last sentence is, well,
> useless. Can you explain why is a necessity to accept that people do
> things against documentation and write stored procedure with RETURNS
> clauses but without SUSPEND statements?

Ehm. How about an executable procedure with output parameters?

Nothing wrong with that.

With regards,

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