Re: PROBLEM CALLING FUNCTIONS WHICH ALL WORKED WHEN THEY WERE PROCEDURES

On 26 Oct 1996 03:21:25 GMT, "R. PERSONEN" <PERSONEN.OHIO_at_postoffice.worldnet.att.net> wrote:

>I USE THE FOLLOWING TEXT FILE (TEST_FUNCT) TO CALL A FUNCTION USING THE
>PERSONAL ORACLE7 FOR WIN95.
>
>DECLARE
>RECV_NUM NUMBER;
>RECV_NUM := FUNCTION_NAM(FUNCTION PARAMETERS);
>/
>
>
>***** WHEN I TRY TO EXECUTE THE ABOVE BY USING "START C:\TEST_FUNCT;"
>COMMAND, ORACLE SENDS BACK A COMMAND THAT IT WAS LOOKING FOR SOMETHING
>ELSE WHEN IT ENCOUNTERED THE "=" SIGN. WHEN I "START C:\FUNCTION_NAM" I
>GET A MESSAGE THAT THE FUNCTION WAS PROPERLY CREATED. I ORIGINALLY HAD
>THE FUNCTIONS AS PROCEDURES AND THEY ALL WORKED. NO I WANT TO RETURN
>ERROR CODES AND NEED THEM TO BE FUNCTIONS. I KNOW HOW TO DO THE SAME
>THING WITH PROCEDURES I JUST WANTED TO TRY IT AS A FUNCTION. THERE MUST BE
>SOMETHING I AM OVERLOOKING SUCH AS HOW TO CALL THE FUNCTION. TO CALL
>PROCEDURES I USED THE "EXECUTE" COMMAND. IS THERE SOMETHING LIKE THIS FOR
>FUNCTIONS?
>

If you are sure that your function compiled cleanly, you might want to enclose your code inside a begin... end; block after the variable declaration. Received on Sat Oct 26 1996 - 00:00:00 CEST