Hi Lester,

> > I think the suspend is the bit where the procedure stalls long enough
> > for the calling routine to print a row or process the row.
> > If you only use procedure to massages data etc, you prolly have no need
> > of a suspend.
>
> Or put another way. You need SUSPEND if you are accessing
> multiple records. Each execution of the SP gives the next
> record.
> Or so I understand it :)

You need SUSPEND if you want the procedure to return a resultset
when doing a SELECT. If you're calling your procedures with EXECUTE,
it is of no use and will suspend :-) your procedure execution.


With regards,

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