Xref: alice comp.databases.oracle.misc:27054
Path: alice!news-feed.fnsi.net!news.he.net!newsserver.pacific.net.sg!not-for-mail
From: ssts <ssts@pacific.net.sg>
Newsgroups: comp.databases.oracle.misc
Subject: Re: ora-01002 fetch-out-of-sequence (report 2.5)
Date: Thu, 04 Mar 1999 08:59:46 +0800
Organization: Subscriber of Pacific Internet 
Lines: 47
Message-ID: <36DDDB02.1E4BE912@pacific.net.sg>
References: <36DC8CF2.8572DA9A@pacific.net.sg> <36dd59c7.0@145.227.194.253>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.06 [en] (Win95; I)
To: Mark Gumbs <mgumbs@hotmail.com>

Hi Mark,
    i had checked my report, it is just a simple report without issue any
commits statement.  In report trigger (before parameter form) i had written
select statement in order to get the system date during the parameter form
display

        select sysdate into :app_date from dual;

    I re-structure my query instead of using two table in queries, i'm create
the formulars and placeholder column in order to store the customer's
information from customer table.  When i ran the report, the result are
displayed on screen without any error message, even though i run so many time
the error didn't came out anymore.

    This is why i felt that report 2.5 still not stable yet, i couldn't catched
the logic how it worked.

    Anyway thanks for your information!!


Mark Gumbs wrote:

> The fetch-out-of-sequence occurs when you are using cursors in a loop and
> the cursor is defined 'for_update'.  If in your loop, you issue a COMMIT,
> you will get the fetch out of sequence message.  Well, thats the case in
> PL/SQL anyway.
> IF you are getting this in a report, check that you do not have any commits
> in report level triggers (e.g Between_Page triggers etc).
>
> Hope this helps.
>
> Mark
>
> ssts wrote in message <36DC8CF2.8572DA9A@pacific.net.sg>...
> >Hi, i'm facing the above error when i ran the report on the customer's
> >workstation.  I had try to run few times i found that this error is not
> >occur sometime.  i wanted to know what the reason?  Is it because the
> >query problem?  I have a simple query like :
> >
> >select transaction.custcode, master.custname, ...
> >from transaction, master
> >where transaction.custcode = master.custcode;
> >
> >Hope somebody give me some hint .
> >Thanks!
> >