Error 49 Bad Bind Variable Oracle
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company
Bad Bind Variable In Oracle Forms
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions bad bind variable in oracle trigger Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, pl sql error 49 bad bind variable just like you, helping each other. Join them; it only takes a minute: Sign up Bad bind variable error in Oracle 10g developer form up vote -1 down vote favorite I have created a table named
Bad Bind Variable In Oracle
password CREATE TABLE PASSWORD (USER_ID NUMBER(10) CONSTRAINT PASSWORD_USER_ID_PK PRIMARY KEY, PASSWD VARCHAR2(20) NOT NULL); INSERT INTO PASSWD (USER_ID,PASSWD) VALUES (1,100); INSERT INTO PASSWD (USER_ID,PASSWD) VALUES (2,200); And created a Login form in an Oracle form developer 10g. And I used this code into Login button. DECLARE CURSOR login_cursor IS SELECT user_id, passwd FROM password; user_id_var password.user_id%TYPE; passwd_var password.passwd%TYPE; login_flag BOOLEAN := FALSE; BEGIN OPEN login_cursor; <
Pls 00049 Bad Bind Variable
= user_id_var AND :login_passwd = passwd_var ) THEN Message('You are in'); login_flag := TRUE; exit check_records; END IF; EXIT WHEN login_cursor%NOTFOUND; END LOOP; CLOSE login_cursor; IF( NOT login_flag ) THEN Message('INVALID LOGIN'); END IF; clear_form; END; But error message appeared like bad bind variable 'login_user_id' bad bind variable 'login_passwd' What's the solution for this? oracle oracleforms share|improve this question edited Apr 5 '13 at 13:34 Sathya 13.2k1667106 asked Apr 5 '13 at 13:13 Taufiqur Rahman 611 2 I hope that's not used in production anywhere.. plaintext password storage, shudders .. also your login check logic is weird.. why are you going through all records in table instead of checking for the specific username? –Sathya Apr 5 '13 at 13:32 I agree with @Sathya. Not only weird, but slow and unsecure. –DARK_A Apr 8 '13 at 11:22 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote Form variables are referenced using :block_name.item_name. You're using :login_user_id which seems to be missing the reference to block, hence Forms is not able to reference the variable and seems to thing it's a bind variable, which it's not. Correct the syntax referencing the variables share|improve this answer answered Apr 5 '13 at 13:25 Sathya 13.2k1667106 I wanna use this code. Please help me to compl
02 January 2008 01:55 sgona Messages: 5Registered: December 2007 Location: pune Junior Member Hi, When i am creating queryfind in myform, I am getting error in creating the fmx. Like Compilation error on WHEN-BUTTON-PRESSED trigger on FIND item in QF_BLOCK data block: PL/SQL ERROR 49 at line 7, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' PL/SQL ERROR 49 at line 7, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' PL/SQL ERROR 49 at line 9, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' Plzzz help me. [MERGED by LF: please, do not open a new topic about the same problem. There is a "REPLY" http://stackoverflow.com/questions/15834905/bad-bind-variable-error-in-oracle-10g-developer-form button in there to continue discussion.] [Updated on: Wed, 02 January 2008 04:25] by ModeratorReport message to a moderator Re: bad bind variable error when creating queryfind. [message #290932 is a reply to message #290907] Wed, 02 January 2008 04:00 mintomohan Messages: 104Registered: November 2006 Location: India Senior Member hi, Can u pls attach the fmb Minto Report message to a moderator http://www.orafaq.com/forum/t/94940/ bad bind variable error when creating queryfind. [message #290939 is a reply to message #290907] Wed, 02 January 2008 04:13 sgona Messages: 5Registered: December 2007 Location: pune Junior Member Hi, Thans for u r reply.I am attaching fmb here. When i am creating queryfind in myform, I am getting error in creating the fmx. Like Compilation error on WHEN-BUTTON-PRESSED trigger on FIND item in QF_BLOCK data block: PL/SQL ERROR 49 at line 7, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' PL/SQL ERROR 49 at line 7, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' PL/SQL ERROR 49 at line 9, column 1 bad bind variable 'PARAMETER.G_QUERY_FIND' It is compling successfully. But when i am generating fmx it is giving error. Plzzz help me. Attachment: APINVOICEFORM1.fmb (Size: 556.00KB, Downloaded 402 times) Report message to a moderator Re: bad bind variable error when creating queryfind. [message #290943 is a reply to message #290907] Wed, 02 January 2008 04:22 Littlefoot Messages: 20835Registered: June 2005 Location: Croatia, Europe Senior MemberAccount Moderator Does your form contain a block named 'parameter'? Is there an item called 'g_query_find'? Report message to a moderator Re: bad bind variable error when creating queryfind. [mes
onXXXXXXXdata block... Compilation error on KEY-NXTBLK trigger onXXXXXXXdata block: PL/SQL http://www.oracleebs.net/2011/07/forms-error-bad-bind-variable.html ERROR 49 at line 1, column 1 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 1, column 1 bad bind variable http://oracleappstechnology.blogspot.com/2009/03/forms-compilation-errors.html 'parameter.G_query_find' PL/SQL ERROR 49 at line 3, column 1 bad bind variable 'parameter.G_query_find' Compiling WHEN-NEW-BLOCK-INSTANCE trigger on XXXXXXX data block... Compilation error bad bind on WHEN-NEW-BLOCK-INSTANCE trigger onXXXXXXXdata block: PL/SQL ERROR 49 at line 3, column 2 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 3, column 2 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 5, column 2 bad bind variable 'parameter.G_query_find' ....Compilation errors have bad bind variable occurred. Form not created ********************** Cause :FORMS60_PATH not properly set or incorrect Solution: SetFORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource In your shell simply execute FORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource This should solve the problem Posted by Ranjith prabu at 4:12:00 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: f60gen, FORMS60_PATH, Oracle applications, parameter.G_query_find 4 comments: NataliaFebruary 17, 2012 at 7:20 AMI do have encountered these errors many times and finally found a solution and the reason behind it through your post. I tried to manipulate so many things to remove this error but everything failed. Thanks for suggesting this nice solution.sap software trainingReplyDeleteRanjith prabuFebruary 17, 2012 at 9:57 PMNatalia. Happy that it helped you..ReplyDeleteBlue_23July 4, 2012 at 1:52 AMHello,I am new to oracle.. I would like to ask what do you mean by this.."In your shell simply executeFORMS60_PATH=$FORMS60_PATH:$AU_TOP/f
parameter.G_query_find Recently all custom forms compilation failed with errors like these:FRM-18108: Failed to load the following objects.Source Module:APPSTAND Source Object: STANDARD_PC_AND_VASource Module:APPSTAND Source Object: STANDARD_TOOLBARSource Module:APPSTAND Source Object: STANDARD_CALENDARCompiling package specification APP_CUSTOM... No compilation errors.orCompiling KEY-NXTBLK trigger on QUERY_FIND data block...Compilation error on KEY-NXTBLK trigger on QUERY_FIND data block:PL/SQL ERROR 49 at line 1, column 1bad bind variable 'parameter.G_query_find'PL/SQL ERROR 49 at line 1, column 1bad bind variable 'parameter.G_query_find'PL/SQL ERROR 49 at line 3, column 1bad bind variable 'parameter.G_query_find'It turned out that FORMS60_PATH was not set correctly. Whenever forms are compiled FORMS60_PATH is set to:FORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resourceIn context file it was set as:$AU_TOP/resource:$AU_TOP/resource/stubAfter correcting this and compiling manually it worked. To make this permanent change the s_f60path to include $AU_TOP/forms/US:$AU_TOP/resource Posted by Vikram Das at 9:32 AM Labels: FRM-18108, parameter.G_query_find 2 comments: Galarza said... thanks June 29, 2009 at 11:43 AM Anonymous said... Hi i am facing the same problem FRM-18108: Failed to load the following objects. Source Module:APPSTAND.fmb Source Object: STANDARD_FOLDERSource Module:APPSTAND Source Object: STANDARD_PC_AND_VASource Module:APPSTAND Source Object: STANDARD_TOOLBARSource Module:APPSTAND Source Object: STANDARD_CALENDARCompiling package specification APP_CUSTOM... No compilation errors. Compiling package specification XXFIN_GBL_CREDITMEMO_PKS... No compilation errors. Compiling package specification XXFIN_GBL_QUERY_PKS... No compilation errors. Compiling package specification XXFIN_GBL_MAIN_PKS... No compilation errors. Compiling package body APP_CUSTOM... No compilation errors. Compiling package body XXFIN_GBL_CREDITMEMO_PKS... No compilation errors. Compiling package body XXFIN_GBL_QUERY_PKS...Compilation error on package body XXFIN_GBL_QUERY_PKS:PL/SQL ERROR 49 at line 102, column 13bad bind variable 'parameter.g_query_find'PL/SQL ERROR 49 at line 102, column 13bad bind variable 'parameter.g_query_find'PL/SQL