The dreaded frm-92101 when executing a database package :-(

Question

Hiya gang! Forms 10g on WIN2K hitting oracle database 10g.
We have a database package with a function that calls the oracle dbms_ldap functions to do an ldap lookup in order to verify an ID. I can run it from SQL/Plus and it returns just fine.
Connected with the same ID in forms causes frm-92101 (forms server failure) to happen. I know this is a catch-all error (which drives me nuts, this is a tool written for developers, by developers, we need more info to troubleshoot errors for crying out loud!) but I'm hoping someone out here will have run across this. Here's the code just in case:
        rc PLS_INTEGER;
     rc := ldap_security.ldap_login_verify(:control.login, :control.passwd);
     if rc = 1 then
          message('verified',acknowledge);
     else
          message('verification failed',acknowledge);
     end if;Now I don't believe its the function itself, as it runs just fine from SQL/Plus. It's got to be something to do with calling it from forms.
I put it up on the app server (solaris) and I get the same error there as when running it from my PC.
Has anyone had success with validating via ldap from forms?
Thanks for any info,
Gary
Message was edited by:
Gary

Answer 1

DOH!
Just before the call to the ldap_security function, I issue a logon statement. The trouble was, I had originally coded an on_logon trigger with the text of "null;" when I created the form and promptly forgot about it.
When logon was called, control went to the on-logon trigger which just exits. It bombed because I wasn't really logged in! You mean to tell me forms could not tell me I wasn't logged in but just gave the frm-92101 error!?
If you issue a select without being logged in, you get a "not connected to Oracle" message. If you try to run a database function inside a package, you get the frm-92101 error.
Anyway, I deleted the on-logon trigger and all is good.
Gary
Message was edited by:
Gary