Forms Internal Error [60604]

[peterlon]

When loading and compiling a form already successfully compiled
during previous work session
or even during the same work session, it happens very often we
obtain something like this:

Compiling procedure SET_CAMPI_INF_SPECIFICHE...
Compilation error on procedure SET_CAMPI_INF_SPECIFICHE:
PL/SQL ERROR 801 at line 1, column 1
internal error [60604]
PL/SQL ERROR 0 at line 14, column 5
Statement ignored
PL/SQL ERROR 801 at line 1, column 1
internal error [60604]
PL/SQL ERROR 0 at line 15, column 5
...

When checking the PL/SQL lines which generated the errors we find
they are comment lines.
We always solve the problem converting the binary form into text
format and then convert back from text to binary (i.e. we use the
File-->Administration-->Convert feature) and thrn reloding the
"regenerate" form.
This procedure of course is both annoying (time consuming!) and
unusual! We look for a way to solve this problem definitively!
Can you tell us something in this respect.
Thank in advance,

Andrea Peterlongo

P.S. We found this problem both with Forms 5.0 and Forms Version
6.0.5.32.0 installed on different WindowsNT 4.0 ws.

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

[Christoph Wagner]

we sometimes have the same problem.

we solve it by, closing and reopening the form (no conversion needed)
sometimes you have to reconnect to the DB

hth christoph

[Marco Nicolazzo]

We solve this problem by saving form and then revert it back (file+revert).

Marco Nicolazzo

Christoph Wagner <christop...@gamed.com> wrote in message
8fu2sb$64h$1...@readme.inode.at...

[Dr. Hans-Dieter Wehe]

We have a similar problem, we can solve rather fast. maybe it works
for you also:
Close the pl/sql-editor then use ctrl-k (kompile) and then
shift-ctrl-k (compile all). This goes fast and our erro disappears.
regards
hans-dieter

peterlon schrieb:

[Matt B.]

"Christoph Wagner" <christop...@gamed.com> wrote in message

news:8fu2sb$64h$1...@readme.inode.at...

> we sometimes have the same problem.
>
> we solve it by, closing and reopening the form (no conversion needed)
> sometimes you have to reconnect to the DB
>
> hth christoph

Yes - I've had the same problem at my last company and at my current one, both
Forms 5.0 and 6.0. The only solution I know of is to save the .fmb, close out
of Developer, and reopen it.

-Matt

[Sprinkles !]