At 11:38 AM 07-11-02 +0000, you wrote:

>--- In IBObjects@y..., Helen Borrie <helebor@t...> wrote:
> >
> > Marco,
> > It's probably a silly question, but what's the point of this block of code?
> >
> > Helen
>Sorry, but I don't speak very well, so I can interprete "point" as a)
>"position" and b) "purpose".

Purpose.

>a) is in a procedure, not in a event
>b) in my post (and in my tests) I've taken away non relevant code. The
>underlaying table is of type "ID, BLOB", so I search for the ID and
>retrieve the blob to put in a string list. So with the Where part I select
>only one record, with ApiFirst I "open" the cursor and go there, read the
>blob, then close. The real code is:
>...
>crsParamPgm.APIFirst;
>crsParamPgm.FieldByName('PARAMETRI').AssignTo(FParamPgm);
>crsParamPgm.Close;
>...
>If you read my second post, you find that clearing the SQL for every use
>of the cursor eliminates the problem. Another solution that works is set
>AutoCommit to true and not perform explicit transaction start/commit.

I just can't see why you have to start and commit a transaction each time
you run this query, is all, since you don't appear to be doing any
DML. Neither do I understand why you close the cursor each time. You
simply need to call First to refresh it.

>So seems that something in IB_Cursor is not cleared properly when .Cursor
>is issued (btw, what about a chapter in GSG that describes exactly all the
>steps for transaction and query/storedproc/cursor usage?).

That's probably easier for you to answer right now than for me (I'm
actually working at the moment...with a big database and several
utilities...) Describes *exactly* *all the steps* ? I guess it depends
which you are talking about, since each (except SP) has its own
section...just use the index. But I don't think you're going to find
instructions for what you're describing. It doesn't sound like a very
"normal" sort of task to me.

Helen