Re: SQL FORMS 3.X Bug using sequences.

In article 3vb_at_u.cc.utah.edu, mem8321_at_u.cc.utah.edu (Mark Miller) writes: In article 3vb_at_u.cc.utah.edu, mem8321_at_u.cc.utah.edu (Mark Miller) writes:
>
>Hello. I have a very irritating bug using sequences in procedures and
>triggers in SQL*FORMS 3.X running on Oracle 6.0.36 for Interactive Unix on
>a 486DX2/66.
>
>One out of every ten or so times I generate a form containing PL/SQL
>statements that refer to sequences I get an error like the following:
>
>Internal PL/SQL #21000. Please contact your Oracle representative.
>
>The only way I can get around this is to save my form (which takes over 30
>seconds on an unloaded system), exit SQL*FORMS, enter it again, load the
>form (another 10 seconds), and re-Generate.
>
>Any suggestions?
>
> Thanks,
> Mark.
>
>
>
>B.T.W. Why does SQL*FORMS take so long to save? Can't it save only the
>records that have changed?
>

We had the same problem... Try referencing the sequence variable by its owner. That seemed to work for us. Also, if you are selecting from DUAL, you need to be sure and reference it as SYS.DUAL. Forms3.0 is sort of funny about that..

Good Luck

mwc Received on Mon Aug 15 1994 - 13:05:33 CEST