Subject | Re: [ib-support] Re: Can SLCODE 100 be trapped in an SP? |
---|---|
Author | Bill Katelis |
Post date | 2002-10-18T01:06:19Z |
Alexander,
Sorry - for the brief (and not detailed post) - I was very frustrated at
the time since I thought it was
so simple.
Yes - I can work around it using a 'select count(*)' or checking that
the host variable is not null.
Now I am intrigued - why would it be set to 100 given that that is the
'not found' condition ?
thanks
bill
Alexander V.Nevsky wrote:
Sorry - for the brief (and not detailed post) - I was very frustrated at
the time since I thought it was
so simple.
Yes - I can work around it using a 'select count(*)' or checking that
the host variable is not null.
Now I am intrigued - why would it be set to 100 given that that is the
'not found' condition ?
thanks
bill
Alexander V.Nevsky wrote:
>--- In ib-support@y..., Bill Katelis <bill@s...> wrote:
>
>
>>Platform: SCO Interbase 5.5
>>
>>Can SQLCODE 100 be trapped in an SP as follows ...
>>
>>WHEN SQLCODE 100 DO
>>BEGIN
>> ........
>>END
>>
>>if so - I can't get it to work...
>>
>>
>
> Bill, AFAIK every successfully performed statement set this system
>global to 100, so it senseless to trap. I recall about 8 years ago,
>being newbie in SQL world, I had some idea which "required" it, but
>can't remember what it was. If you explain your aim, perhaps we can
>discuss suitable solution.
>
>Best regards, Alexander V.Nevsky.
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>