Ok, makes sense. So If you are just returning one row, no suspend needed,
the EXIT would suffice in my case..

Im still not clear about the null thing.. In a stored proc, I thought the
only way to know if a select statement didnt find any result was to look at
a key value and see if its NULL. If so, you would know if a row was
returned. Not so? If not, how do you know (using raw sql) if no row was
returned??


Gordon Hamm
Voice Data Systems Inc.
435-635-7464

----- Original Message -----
From: "Helen Borrie" <helebor@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, August 14, 2001 10:50 AM
Subject: Re: [IBO] Wrong record..


> At 10:35 AM 14-08-01 -0600, you wrote:
> >Thanks, those are great clues. One question though, I thought you needed
to
> >use suspend even if you wanted to only return one row.
> >Not true??
>
> No: the purpose of SUSPEND is to hold the output back and wait for
another row, so you place it at the end of a FOR SELECT...DO... loop.
>
> 'night
>
> Helen
>
> All for Open and Open for All
> InterBase Developer Initiative · http://www.interbase2000.org
> _______________________________________________________
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>