StoredProcHasDML will make IBO aware that you are doing this.
One thing to be careful about is the stored procedure may be executed in
full on the server but your fetches may not actually bring all records to
the client. Records are prefetched into batches which means more rows will
be produced on the server than actually are fetched into the client buffers.
Using FOR UPDATE just might be a way to make it only process a single record
at a time on the server.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Svein Erling Tysvær" <svein.erling.tysvaer@...>
To: <ibobjects@yahoogroups.com>
Sent: Tuesday, September 18, 2001 1:55 AM
Subject: Re: [IBO] Stored Procedure half-Select half-Executable


> >I know SUSPEND is not recommended for Select-Procedures
>
> I think it is the other way around, SUSPEND is only recommended for select
> procedures.
>
> >Has anyone any idea or advice?
>
> Never done anything like it. The one thing I would be careful to check, is
> how IBO reacts to something like this. Will it know that changes have been
> done? Maybe you have to set RequestLive to true (doubt it) or change your
> logic to make it two procedures, but I don't know. Do you have any
> particular problems?
>
> Set
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>