"compiled with errors"

[cmj]

I am using v7.0.2.1076. It seems to me that since I began using 7.0 that I sometimes simply get the message "compiled with errors" when I compile a package body in the program window. The compile errors are not listed. It happens rarely enough that I have not yet noted if there is a pattern to the reasons the code didn't compile. This time I'm working on an urgent problem so it is particularly irritating that it doesn't tell me WHAT ERRORS made it fail to compile.

Do I have some setting wrong?

 

[MikeM]

What does compiling in SQL*Plus show?

 

[cmj]

When I compile in SQL+ it shows:
Warning: Package Body created with compilation errors.

SQL> show errors
Errors for PACKAGE BODY BLBILMAK:

LINE/COL ERROR
-------- -----------------------------------------------------------------
4682/13 PL/SQL: SQL Statement ignored
4720/16 PLS-00390: undefined column 'USED_BY_BUDGET_BILLING_IND' in
INSERT statement

 

[cmj]

AH HA! I think I've got it, and the problem is the same one as another posting to which I have added a reply about the test option not being in the menu when I right-click a program in a package.

Both packages are oldsters and have long lists of "rem" comments, their modification history, at their beginning. When I remove those commments both problems go away: I get a list of errors rather than the lonely little "compiled with errors" message, and when the package compiles without errors the Test option appears in the menu when I right-click a program in the package.

I had the exact same problem when I first began using PL/SQL Developer, although I don't remember the exact error I encountered. It was the reason I logged my very first question in this forum. I discovered at that time that there is some magic number of characters you can have in "rem" comments; after that errors arise. I solved the problem then by changing the comment prefix to "--", which worked just fine. The trouble is that the standard here is "rem" and I am the only developer using your product.

Since I am an old programmer, I have a tiney little retention span for problems like this. I am bound to encounter it again one day unless you can fix it, and I'll have to be back here asking the same old question.

I love this forum and I love PL/SQL Developer. Keep up the good work, fix this problem, and let's all get on with the job.

Thank you!