Re: Reports 2.5 problem

From: Joseph Dane <jdane_at_honlab.nmfs.hawaii.edu>
Date: 1997/03/13
Message-ID: <wo913r64rh.fsf_at_menpachi.nmfs.hawaii.edu>#1/1

>>>>> "George" == George Rapp <gwr_at_oasis.novia.net> writes:

    George> I saw this error when I had not GRANTed SELECT on a table
    George> referenced in one of my report triggers (BEFORE PARAMETER
    George> FORM) to anybody but SYSTEM.  Since I develop reports as
    George> SYSTEM, I could see the table fine; anybody else got the
    George> error message you mentioned above.

I have also seen this, but with Reports 2.0 and what I think is a different cause. I recently added a placeholder which calls a function which opens a cursor. r20run dies even beore it can prompt for userid/password, apparently because it hasn't connected to the database yet and can't resolve the table name in the cursor's SELECT.

Go figure.

Joe Received on Thu Mar 13 1997 - 00:00:00 CET

This message: [ Message body ]
Next message: jacob.marley_at_plaintalk.bellevue.wa.us: "Looking for a method to encrypt data within an Oracle database, hosted on a public net, and accessed by thousands"
Previous message: Richard Brandl: "Licensing of stored procedures"
Maybe in reply to: Aram Meguerian: "Re: Reports 2.5 problem"
Next in thread: QuadTwin: "Re: Best point to commit in a Master/Dtl Form"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message